Lines Matching refs:all

17 the same order in all contexts.  That is directly under control of
29 from a global counter.  In case of deadlock while locking all the buffers
32 younger task) unlocks all of the buffers that it has already locked, and then
37 needs to back off and drop all the locks it is currently holding, i.e. the
60   after having dropped all already acquired locks. These functions have the
65   contending lock (after having dropped all other already acquired locks) will
66   work correctly. After all if no other ww mutex has been acquired yet there's
74   - When full debugging is enabled ww_mutex_lock_slow checks that all acquired
87 Of course, all the usual variants for handling wake-ups due to signals are also
211 and edges can only be changed when holding the locks of all involved nodes. w/w
233 when the dynamic locking step hits -EDEADLK we also need to unlock all the
315   would add overhead to all cases where normal mutexes are used, and
327      unlocking all mutexes.
329      before unlocking all mutexes.