Searched full:potential (Results 1 – 25 of 855) sorted by relevance
12345678910>>...35
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
50 * be executed due to potential deadlocks to be run at a later call when the57 * 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
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.
69 The kernel security team strongly recommends that reporters of potential77 not contribute to actually fixing any potential security problems.
48 identified a potential hardware flaw.110 or anyone becomes aware of a potential violation, please report it304 to participate in the communication send a list of potential subscribers to
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")
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()
27 * and a mask of potential interrupt lines is returned.142 * @val: mask of potential interrupts (unused)
1 - Move to threaded_irqs to mitigate potential infinite loop in ivpu_ipc_irq_handler()
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
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()
29 * is through the potential type field from the PDC_MODEL call.
6 # - ccio before any potential subdevices
4 ** "HP has discovered a potential system defect that can affect
16 even potential distribution ready.
30 # PIO only, or DMA (several potential schemes).
23 /* silence potential warning: conflicting types for 'main' */ in _start_c()
25 * the SP FW could indicate potential performance issue
33 # first (if it exists). Additionally, potential clock counting sources
