Searched refs:caught (Results 1 – 25 of 34) sorted by relevance
12
/linux-6.6.21/fs/proc/ |
D | array.c | 267 sigset_t pending, shpending, blocked, ignored, caught; in task_sig() local 276 sigemptyset(&caught); in task_sig() 282 collect_sigign_sigcatch(p, &ignored, &caught); in task_sig() 300 render_sigset_t(m, "SigCgt:\t", &caught); in task_sig()
|
/linux-6.6.21/sound/parisc/ |
D | harmony.c | 489 unsigned long caught; in snd_harmony_capture_pointer() local 498 caught = rcuradd - h->cbuf.addr; in snd_harmony_capture_pointer() 502 rcuradd, h->cbuf.addr, caught); in snd_harmony_capture_pointer() 509 return bytes_to_frames(rt, caught); in snd_harmony_capture_pointer()
|
/linux-6.6.21/Documentation/mm/ |
D | vmalloced-kernel-stacks.rst | 26 overflows to be caught immediately rather than causing difficult to 64 with guard pages. This causes kernel stack overflows to be caught
|
D | page_owner.rst | 53 are caught and marked, although they are mostly allocated from struct
|
/linux-6.6.21/Documentation/admin-guide/cgroup-v1/ |
D | freezer-subsystem.rst | 25 from within the tasks we wish to freeze. While SIGSTOP cannot be caught, 27 SIGCONT is especially unsuitable since it can be caught by the task. Any
|
/linux-6.6.21/drivers/accessibility/speakup/ |
D | DefaultKeyAssignments | 44 synth until it has caught up with what is being printed on the
|
/linux-6.6.21/arch/arm/mach-s3c/ |
D | Kconfig | 57 one bank to another to be caught, at the expense of using a little
|
/linux-6.6.21/Documentation/powerpc/ |
D | kasan.txt | 24 stack issues that cannot be caught with outline mode.
|
/linux-6.6.21/Documentation/arch/arm/ |
D | memory.rst | 93 space are also caught via this mapping.
|
D | porting.rst | 107 of the mapped memory map) to be caught. Normally set to 8MB.
|
/linux-6.6.21/Documentation/arch/x86/ |
D | buslock.rst | 122 is exceeded then any task which is caught via the buslock #DB exception is
|
/linux-6.6.21/Documentation/admin-guide/device-mapper/ |
D | log-writes.rst | 52 which isn't quite what happened and wouldn't be caught during the log replay.
|
/linux-6.6.21/Documentation/trace/ |
D | mmiotrace.rst | 124 are not caught, since the mapping always exists and is returned directly.
|
/linux-6.6.21/Documentation/process/ |
D | 4.Coding.rst | 232 automated way. Any problem caught by the computer is a problem which will 415 ensure that code which has not been updated is caught by the compiler.
|
/linux-6.6.21/Documentation/bpf/ |
D | ringbuf.rst | 197 being available after commit only if consumer has already caught up right up to
|
/linux-6.6.21/Documentation/filesystems/ |
D | autofs.rst | 111 directory without some way to avoid getting caught in the trap. For 141 caught in the mount trap.
|
/linux-6.6.21/Documentation/livepatch/ |
D | reliable-stacktrace.rst | 88 even if not caught by other checks, it is strongly recommended that
|
/linux-6.6.21/Documentation/virt/kvm/x86/ |
D | timekeeping.rst | 584 delivered, and after which, the guest time may need to be caught up. NTP may 594 always be caught up to the original rate. KVM clock avoids these problems by
|
/linux-6.6.21/Documentation/locking/ |
D | ww-mutex-design.rst | 368 as possible. Some common api abuses will be caught with
|
/linux-6.6.21/Documentation/hwmon/ |
D | sysfs-interface.rst | 59 between readings to be caught and alarmed. The exact definition of an
|
/linux-6.6.21/arch/m68k/ifpsp060/src/ |
D | pfpsp.S | 3160 # exceptions, they won't pass through here since they are caught 3718 # exceptions, they won't pass through here since they are caught
|
/linux-6.6.21/Documentation/kernel-hacking/ |
D | hacking.rst | 646 which were caught before). Usually this is accompanied by a fairly
|
/linux-6.6.21/Documentation/scsi/ |
D | st.rst | 98 are caught at that point, but this takes time. In some applications, several
|
/linux-6.6.21/arch/ |
D | Kconfig | 1246 caught immediately rather than causing difficult-to-diagnose
|
/linux-6.6.21/Documentation/userspace-api/media/v4l/ |
D | hist-v4l2.rst | 810 ``/dev/vout`` which never caught on were replaced by ``/dev/video``.
|
12