Searched full:potential (Results 1 – 25 of 957) sorted by relevance
12345678910>>...39
4 There is a potential for deadlock when allocating a struct sk_buff for9 not been observed, but it would be nice to eliminate any potential for16 efficiently allocate sk_buffs without introducing any potential for
20 * @chain: potential dma_fence_chain, but can be other fence as well24 * @array: potential dma_fence_array, but can be other fence as well44 * potential fences in them. If @head is just a normal fence only that one is
69 * be executed due to potential deadlocks to be run at a later call when the76 * due to potential deadlocks. If SHRINK_STOP is returned, then no further
7 * on most operations but not ->writepage as the potential stall time
20 * size vs number of potential users that could benefit
50 * outside the kernel. Values 1-99 are reserved for potential76 * outside the kernel. Values 1-99 are reserved for potential
68 with other potential users for precise timers gives another reason to71 Another potential benefit is that such a separation allows even more123 potential for code sharing either.
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")
16 * will be set as well to prevent potential compilation failures.
27 * and a mask of potential interrupt lines is returned.142 * @val: mask of potential interrupts (unused)
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()
17 potential Linux kernel security issues. This assignment is independent46 and the team there will work with you on it. Note that no potential
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()
16 … "PublicDescription": "Indirect Branch Prediction for potential multi-target branch (speculative)."
8 is 32 - higher value means more potential throughput but more
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 better552 avoid potential detection issues.757 - Significant discrepancies indicate potential issues in the data path
110 potential issues thanks to the call to :manpage:`execveat(2)` with121 The threat is (potential) malicious scripts run by trusted (and not fooled)
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()
90 * @parent: Pointer to a potential parent struct device. If set to158 * @parent: Pointer to a potential parent struct device. If set to
29 * is through the potential type field from the PDC_MODEL call.
4 ** "HP has discovered a potential system defect that can affect
6 # - ccio before any potential subdevices
16 * the SP FW could indicate potential performance issue
30 # PIO only, or DMA (several potential schemes).