Searched refs:deadlocks (Results 1 – 25 of 26) sorted by relevance
12
77 unsigned long deadlocks; member316 __this_cpu_inc(ptcstats.deadlocks); in sn2_global_tlb_purge()340 __this_cpu_inc(ptcstats.deadlocks); in sn2_ptc_deadlock_recovery()509 stat->deadlocks, in sn2_ptc_seq_show()
9 can occur deadlocks while handling isr.
10 can occur deadlocks while handling isr.
93 ww mutex have been released (preventing deadlocks) and makes sure that we375 - Normal lockdep errors that can result in deadlocks.377 Some of the lockdep errors that can result in deadlocks:380 - 'normal' deadlocks that can occur.
82 to lock recursion deadlocks.89 because this could lead to lock inversion deadlocks. (The validator233 example, complex deadlocks that would normally need more than 3 CPUs and
98 - Detects multi-task circular deadlocks and prints out all affected
113 play with the spinlock is that you can get deadlocks:
34 file with flock(). With pre 1.3.96 kernels this could result in deadlocks that,
235 deadlocks you must treat :c:func:`jbd2_journal_start` /238 deadlocks. Note that :c:func:`jbd2_journal_extend` has similar blocking
210 in all cases except some malicious deadlocks
168 This introduces lots of scope for deadlocks with transactions that are already527 The problem with this is that it can lead to deadlocks as we may need to commit546 up front. This avoids deadlocks and removes a blocking point from the
267 This may also be done to avoid internal deadlocks, but rarely.
12 allocating memory to prevent recursion deadlocks caused by direct
45 including proneness to deadlocks around the single execution context.145 pressure. Else it is possible that the worker-pool deadlocks waiting
8 deadlocks and the like.
61 deadlocks when using in a nested fashion, and so it is not recommended for
19 __GFP_IO allocation requests are made to prevent file system deadlocks.
49 avoid deadlocks with garbage collection -- the VFS will lock the i_sem
129 deadlocks.
112 deadlocks. The late revelation of these problems - and refusal to
230 device. In order to avoid deadlocks, it is recommended that the locks
187 acquire the spinlock. Such deadlocks can be avoided by using
1069 related deadlocks before they actually occur.1120 deadlocks (lockups) to be detected and reported automatically.1130 deadlocks are also debuggable.
389 not to introduce deadlocks.
609 deadlocks, e.g. avoid trying to allocate more memory from the pool while
