Searched refs:deadlocks (Results 1 – 25 of 25) sorted by relevance
76 unsigned long deadlocks; member314 __this_cpu_inc(ptcstats.deadlocks); in sn2_global_tlb_purge()337 __this_cpu_inc(ptcstats.deadlocks); in sn2_ptc_deadlock_recovery()497 stat->deadlocks, in sn2_ptc_seq_show()
10 can occur deadlocks while handling isr.
75 ww mutex have been released (preventing deadlocks) and makes sure that we336 - Normal lockdep errors that can result in deadlocks.338 Some of the lockdep errors that can result in deadlocks:341 - 'normal' deadlocks that can occur.
48 consideration of deadlocks with lg_global_lock.52 are needed in the non-RT kernels to prevent deadlocks like:
82 to lock recursion deadlocks.89 because this could lead to lock inversion deadlocks. (The validator186 example, complex deadlocks that would normally need more than 3 CPUs and
112 - 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,
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
257 This may also be done to avoid internal deadlocks, but rarely.
8 deadlocks and the like.
100 greatly simplifies locking hierarchies and helps avoid deadlocks.
13 __GFP_IO allocation requests are made to prevent file system deadlocks.
73 deadlocks when using in a nested fashion, and so it is not recommended for
49 avoid deadlocks with garbage collection -- the VFS will lock the i_sem
51 including proneness to deadlocks around the single execution context.150 pressure. Else it is possible that the worker-pool deadlocks waiting
115 deadlocks.
3317 device. In order to avoid deadlocks, it is recommended that the locks
107 deadlocks. The late revelation of these problems - and refusal to
927 deadlocks (lockups) to be detected and reported automatically.937 deadlocks are also debuggable.996 related deadlocks before they actually occur.
504 acquire the spinlock. Such deadlocks can be avoided by using
367 not to introduce deadlocks.
546 to better handle low memory problems (and potential deadlocks).
610 deadlocks, e.g. avoid trying to allocate more memory from the pool while