Searched full:potential (Results 1 – 25 of 969) sorted by relevance
12345678910>>...39
| /linux-6.15/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
|
| /linux-6.15/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 | 69 * be executed due to potential deadlocks to be run at a later call when the
76 * 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
|
| D | rbtree_types.h | 20 * size vs number of potential users that could benefit
|
| /linux-6.15/Documentation/gpu/nova/ ! |
| D | guidelines.rst | 46 semantical sense of the structure, as well as potential locking and lifetime
51 semantical behavior must be explained including potential special or corner
55 must be fully documented. This includes doc comments, potential locking and
|
| /linux-6.15/include/uapi/linux/ ! |
| D | lsm.h | 50 * outside the kernel. Values 1-99 are reserved for potential
76 * outside the kernel. Values 1-99 are reserved for potential
|
| /linux-6.15/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.
|
| /linux-6.15/security/landlock/ ! |
| D | domain.h | 65 /* Adds 11 extra characters for the potential " (deleted)" suffix. */
82 * @usage: Number of potential children domains plus their parent
|
| /linux-6.15/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.
|
| /linux-6.15/kernel/irq/ ! |
| D | autoprobe.c | 27 * and a mask of potential interrupt lines is returned.
142 * @val: mask of potential interrupts (unused)
|
| /linux-6.15/security/safesetid/ ! |
| D | lsm.c | 207 * Kill this process to avoid potential security vulnerabilities in safesetid_task_fix_setuid()
231 * Kill this process to avoid potential security vulnerabilities in safesetid_task_fix_setgid()
252 * Kill this process to avoid potential security vulnerabilities in safesetid_task_fix_setgroups()
|
| /linux-6.15/Documentation/process/ ! |
| D | cve.rst | 17 potential Linux kernel security issues. This assignment is independent
46 and the team there will work with you on it. Note that no potential
|
| /linux-6.15/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()
|
| /linux-6.15/tools/perf/pmu-events/arch/x86/amdzen1/ ! |
| D | branch.json | 16 … "PublicDescription": "Indirect Branch Prediction for potential multi-target branch (speculative)."
|
| /linux-6.15/Documentation/ABI/testing/ ! |
| D | sysfs-driver-xen-blkfront | 8 is 32 - higher value means more potential throughput but more
|
| /linux-6.15/Documentation/networking/diagnostic/ ! |
| D | twisted_pair_layer1_diagnostics.rst | 48 indicate potential issues at the hardware or physical layer.
88 detected, indicating potential Layer 1 issues like a cable fault,
106 troubleshoot potential physical layer issues.
316 **PSE**. Check for potential issues such as a short circuit in the cable,
397 potential false positives for each test result, users would have a better
552 avoid potential detection issues.
757 - Significant discrepancies indicate potential issues in the data path
|
| /linux-6.15/net/mac80211/ ! |
| D | wme.c | 125 /* Ensure hash is set prior to potential SW encryption */ in ieee80211_select_queue_80211()
154 /* Ensure hash is set prior to potential SW encryption */ in ieee80211_select_queue()
|
| /linux-6.15/Documentation/userspace-api/ ! |
| D | check_exec.rst | 110 potential issues thanks to the call to :manpage:`execveat(2)` with
121 The threat is (potential) malicious scripts run by trusted (and not fooled)
|
| /linux-6.15/arch/parisc/math-emu/ ! |
| D | fpu.h | 29 * is through the potential type field from the PDC_MODEL call.
|
| /linux-6.15/drivers/parisc/ ! |
| D | Makefile | 6 # - ccio before any potential subdevices
|
| D | README.dino | 4 ** "HP has discovered a potential system defect that can affect
|
| /linux-6.15/drivers/base/ ! |
| D | faux.c | 90 * @parent: Pointer to a potential parent struct device. If set to
171 * @parent: Pointer to a potential parent struct device. If set to
|
| /linux-6.15/drivers/staging/media/atomisp/pci/ ! |
| D | ia_css_err.h | 16 * the SP FW could indicate potential performance issue
|
12345678910>>...39