Home
last modified time | relevance | path

Searched refs:killed (Results 1 – 25 of 53) sorted by relevance

123

/Linux-v5.15/Documentation/security/
Dsak.rst50 actually want killed. This is because these applications are
54 You can identify processes which will be killed by SAK with the
65 So ``gpm`` will be killed by SAK. This is a bug in gpm. It should
/Linux-v5.15/net/smc/
Dsmc_tx.c92 conn->killed || in smc_tx_wait()
172 conn->killed) in smc_tx_sendmsg()
519 if (conn->killed) in smcr_tx_sndbuf_nonempty()
580 if (conn->killed || in smc_tx_sndbuf_nonempty()
642 if (conn->killed || in smc_tx_consumer_update()
646 !conn->killed) { in smc_tx_consumer_update()
Dsmc_rx.c210 conn->killed || in smc_rx_wait()
321 if (conn->killed) in smc_rx_recvmsg()
Dsmc_close.c69 smc->conn.killed, in smc_close_stream_wait()
98 if (conn->killed) in smc_close_final()
Dsmc.h208 u8 killed : 1; /* abnormal termination */ member
Dsmc_cdc.c69 if (conn->killed) { in smc_cdc_get_free_slot()
404 if (!conn || conn->killed) in smcd_cdc_rx_tsklet()
/Linux-v5.15/drivers/gpu/drm/nouveau/nvkm/engine/fifo/
Dchangf100.h13 bool killed; member
Dchangk104.h15 bool killed; member
Dgpfifogf100.c173 if (!list_empty(&chan->head) && !chan->killed) { in gf100_fifo_gpfifo_fini()
195 if (list_empty(&chan->head) && !chan->killed) { in gf100_fifo_gpfifo_init()
Dgpfifogk104.c222 if (list_empty(&chan->head) && !chan->killed) { in gk104_fifo_gpfifo_init()
/Linux-v5.15/drivers/gpu/drm/nouveau/
Dnouveau_chan.h54 atomic_t killed; member
Dnouveau_chan.c54 atomic_set(&chan->killed, 1); in nouveau_channel_killed()
63 if (likely(chan && chan->fence && !atomic_read(&chan->killed))) { in nouveau_channel_idle()
154 atomic_set(&chan->killed, 0); in nouveau_channel_prep()
/Linux-v5.15/tools/testing/selftests/rcutorture/bin/
Dkvm-recheck.sh45 echo QEMU killed
/Linux-v5.15/drivers/block/paride/
DTransition-notes106 Corollary 1: ps_tq_active can be killed. Indeed, the only place where we
112 Corollary 2: ps_spinlock can be killed. Indeed, Lemma 1 and Lemma 2 show
118 can be killed. Indeed, we are not holding pd_lock and thus pd_busy is already
/Linux-v5.15/Documentation/vm/
Dovercommit-accounting.rst27 killed while accessing pages but will receive errors on memory
/Linux-v5.15/Documentation/driver-api/firmware/
Dfirmware_cache.rst47 * Upon suspend any pending non-uevent firmware requests are killed to avoid
/Linux-v5.15/tools/testing/selftests/arm64/signal/
DREADME36 - Most of these tests are successfully passing if the process gets killed by
/Linux-v5.15/tools/testing/selftests/arm64/fp/
DREADME20 The test runs until killed by the user.
/Linux-v5.15/Documentation/admin-guide/cgroup-v1/
Dmemcg_test.rst277 will be killed by the kernel.
280 in other groups shouldn't be killed.
/Linux-v5.15/drivers/nvdimm/
Dbus.c553 bool killed; in nd_device_unregister() local
579 killed = kill_device(dev); in nd_device_unregister()
582 if (!killed) in nd_device_unregister()
/Linux-v5.15/Documentation/x86/
Dbuslock.rst109 In this case, the bus lock is not tolerated and the process is killed.
/Linux-v5.15/Documentation/sparc/oradax/
Ddax-hv-api.txt33 …operation may be cancelled or killed via the ccb_kill API function. It is recommended for guest so…
131 referenced by a CCB must be pinned in memory until the CCB either completes execution or is killed
985 … 0x3 Command ran and was killed (partial execution may
1002 0x7 Command was killed
1367 … the virtual machine. It could not be killed and no action was taken.
1376 … will reflect the killed status, with the subsequent implications that
1395 …If the pipeline target CCB is killed but the pipeline source CCB was skipped, the completion area …
1396 … target CCB may contain status (4,0) "Command was skipped" instead of (3,7) "Command was killed".
1398 …If the pipeline source CCB is killed, the pipeline target CCB's completion status may read (1,0) "…
1399 … This does not mean the target CCB was processed; since the source CCB was killed, there was no
[all …]
/Linux-v5.15/fs/
Dexec.c1069 goto killed; in de_thread()
1097 goto killed; in de_thread()
1164 killed: in de_thread()
/Linux-v5.15/drivers/net/wireless/intersil/orinoco/
Dorinoco_usb.c270 int killed; member
329 ctx->killed = 1; in ezusb_request_timerfn()
518 if (ctx->killed) { in ezusb_request_out_callback()
/Linux-v5.15/Documentation/driver-api/usb/
Dcallbacks.rst105 killed by usbcore. Note that in this case disconnect will be called some

123