Searched full:potential (Results 1 – 25 of 1601) sorted by relevance
12345678910>>...65
| /kernel/linux/linux-6.6/Documentation/admin-guide/aoe/ |
| D | todo.rst | 4 There is a potential for deadlock when allocating a struct sk_buff for
9 not been observed, but it would be nice to eliminate any potential for
16 efficiently allocate sk_buffs without introducing any potential for
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/aoe/ |
| D | todo.rst | 4 There is a potential for deadlock when allocating a struct sk_buff for
9 not been observed, but it would be nice to eliminate any potential for
16 efficiently allocate sk_buffs without introducing any potential for
|
| /kernel/linux/linux-6.6/include/linux/ |
| D | dma-fence-unwrap.h | 20 * @chain: potential dma_fence_chain, but can be other fence as well
24 * @array: potential dma_fence_array, but can be other fence as well
44 * potential fences in them. If @head is just a normal fence only that one is
|
| D | shrinker.h | 50 * be executed due to potential deadlocks to be run at a later call when the
57 * due to potential deadlocks. If SHRINK_STOP is returned, then no further
|
| D | migrate_mode.h | 7 * on most operations but not ->writepage as the potential stall time
|
| /kernel/linux/linux-5.10/include/linux/ |
| D | shrinker.h | 47 * be executed due to potential deadlocks to be run at a later call when the
54 * due to potential deadlocks. If SHRINK_STOP is returned, then no further
|
| D | migrate_mode.h | 7 * on most operations but not ->writepage as the potential stall time
|
| /kernel/linux/linux-6.6/Documentation/timers/ |
| D | hrtimers.rst | 68 with other potential users for precise timers gives another reason to
71 Another potential benefit is that such a separation allows even more
123 potential for code sharing either.
|
| /kernel/linux/linux-6.6/Documentation/process/ |
| D | security-bugs.rst | 69 The kernel security team strongly recommends that reporters of potential
77 not contribute to actually fixing any potential security problems.
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/ |
| D | security-bugs.rst | 69 The kernel security team strongly recommends that reporters of potential
77 not contribute to actually fixing any potential security problems.
|
| /kernel/linux/linux-5.10/Documentation/timers/ |
| D | hrtimers.rst | 68 with other potential users for precise timers gives another reason to
71 Another potential benefit is that such a separation allows even more
123 potential for code sharing either.
|
| /kernel/linux/linux-5.10/tools/testing/selftests/bpf/verifier/ |
| D | ref_tracking.c | 2 "reference tracking: leak potential reference",
13 "reference tracking: leak potential reference to sock_common",
24 "reference tracking: leak potential reference on stack",
38 "reference tracking: leak potential reference on stack 2",
53 "reference tracking: zero potential reference",
64 "reference tracking: zero potential reference to sock_common",
75 "reference tracking: copy and zero potential references",
|
| /kernel/linux/linux-6.6/security/safesetid/ |
| D | lsm.c | 206 * Kill this process to avoid potential security vulnerabilities in safesetid_task_fix_setuid()
230 * Kill this process to avoid potential security vulnerabilities in safesetid_task_fix_setgid()
251 * Kill this process to avoid potential security vulnerabilities in safesetid_task_fix_setgroups()
|
| /kernel/linux/linux-6.6/tools/testing/selftests/bpf/progs/ |
| D | verifier_ref_tracking.c | 111 __description("reference tracking: leak potential reference")
126 __description("reference tracking: leak potential reference to sock_common")
141 __description("reference tracking: leak potential reference on stack")
159 __description("reference tracking: leak potential reference on stack 2")
179 __description("reference tracking: zero potential reference")
194 __description("reference tracking: zero potential reference to sock_common")
209 __description("reference tracking: copy and zero potential references")
317 __description("reference tracking: leak potential reference to user key")
332 __description("reference tracking: leak potential reference to system key")
|
| D | pyperf180.c | 16 * will be set as well to prevent potential compilation failures.
|
| /kernel/linux/linux-6.6/kernel/irq/ |
| D | autoprobe.c | 27 * and a mask of potential interrupt lines is returned.
142 * @val: mask of potential interrupts (unused)
|
| /kernel/linux/linux-5.10/kernel/irq/ |
| D | autoprobe.c | 27 * and a mask of potential interrupt lines is returned.
142 * @val: mask of potential interrupts (unused)
|
| /kernel/linux/linux-6.6/drivers/accel/ivpu/ |
| D | TODO | 1 - Move to threaded_irqs to mitigate potential infinite loop in ivpu_ipc_irq_handler()
|
| /kernel/linux/linux-5.10/tools/perf/pmu-events/arch/x86/amdzen1/ |
| D | branch.json | 16 … "PublicDescription": "Indirect Branch Prediction for potential multi-target branch (speculative)."
|
| /kernel/linux/linux-6.6/tools/perf/pmu-events/arch/x86/amdzen1/ |
| D | branch.json | 16 … "PublicDescription": "Indirect Branch Prediction for potential multi-target branch (speculative)."
|
| /kernel/linux/linux-5.10/Documentation/ABI/testing/ |
| D | sysfs-driver-xen-blkfront | 8 is 32 - higher value means more potential throughput but more
|
| /kernel/linux/linux-6.6/Documentation/ABI/testing/ |
| D | sysfs-driver-xen-blkfront | 8 is 32 - higher value means more potential throughput but more
|
| /kernel/linux/linux-5.10/drivers/net/ethernet/dec/tulip/ |
| D | timer.c | 133 /* mod_timer synchronizes us with potential add_timer calls in tulip_media_task()
167 /* mod_timer synchronizes us with potential add_timer calls in comet_timer()
|
| /kernel/linux/linux-6.6/drivers/net/ethernet/dec/tulip/ |
| D | timer.c | 133 /* mod_timer synchronizes us with potential add_timer calls in tulip_media_task()
167 /* mod_timer synchronizes us with potential add_timer calls in comet_timer()
|
| /kernel/linux/linux-5.10/tools/testing/selftests/bpf/progs/ |
| D | pyperf180.c | 16 * will be set as well to prevent potential compilation failures.
|
12345678910>>...65