Searched refs:unlocking (Results 1 – 20 of 20) sorted by relevance
| /Linux-v5.4/Documentation/devicetree/bindings/clock/ |
| D | arm-syscon-icst.txt | 49 unlocking register is located
|
| /Linux-v5.4/Documentation/locking/ |
| D | rt-mutex.rst | 41 locking overhead when locking an uncontended mutex or unlocking a mutex
|
| D | ww-mutex-design.rst | 281 /* need to do that before unlocking, since only the current lock holder is
375 unlocking all mutexes.
377 before unlocking all mutexes.
|
| D | rt-mutex-design.rst | 437 The wait_lock of the mutex is taken since the slow path of unlocking the
517 The unlocking of a mutex also has a fast path for those architectures with
520 take the slow path when unlocking the mutex. If the mutex doesn't have any
528 mutex. This synchronizes the locking and unlocking of the mutex.
|
| D | mutex-design.rst | 83 - Recursive locking/unlocking is not permitted.
|
| /Linux-v5.4/Documentation/ |
| D | robust-futex-ABI.txt | 71 in the middle of a locking or unlocking operation.
116 Actual locking and unlocking, during normal operations, is handled
|
| D | futex-requeue-pi.txt | 21 rest to the natural wakeup inherent in unlocking the mutex
|
| /Linux-v5.4/fs/dlm/ |
| D | dlm_internal.h | 696 struct list_head unlocking; member
|
| D | user.c | 648 INIT_LIST_HEAD(&proc->unlocking); in device_open()
|
| D | lock.c | 6001 list_move(&lkb->lkb_ownqueue, &ua->proc->unlocking); in dlm_user_unlock()
6198 list_for_each_entry_safe(lkb, safe, &proc->unlocking, lkb_ownqueue) { in dlm_clear_proc_locks()
6238 list_for_each_entry_safe(lkb, safe, &proc->unlocking, lkb_ownqueue) { in purge_proc_locks()
|
| /Linux-v5.4/fs/jffs2/ |
| D | README.Locking | 55 lead to deadlock, unless we played games with unlocking the i_sem
|
| /Linux-v5.4/Documentation/filesystems/ |
| D | mandatory-locking.txt | 35 update, before applying its own lock, updating the file and unlocking it again.
|
| D | locking.rst | 332 followed by unlocking it. Once set_page_writeback() has been run against the
|
| D | porting.rst | 44 typically between calling iget_locked() and unlocking the inode.
|
| D | vfs.rst | 311 called when VFS is unlocking a filesystem and making it writable
822 The filesystem must take care of unlocking the page and
|
| D | fscrypt.rst | 254 there is no requirement to support unlocking a file with multiple
|
| /Linux-v5.4/Documentation/vm/ |
| D | unevictable-lru.rst | 426 zeros out the page_mapping of the old page before unlocking it, so m[un]lock
|
| /Linux-v5.4/Documentation/filesystems/caching/ |
| D | netfs-api.txt | 743 associated object before unlocking the cookie.
|
| /Linux-v5.4/Documentation/cdrom/ |
| D | cdrom-standard.rst | 347 However, strategic actions such as ejection of the tray, or unlocking
|
| /Linux-v5.4/Documentation/scsi/ |
| D | ChangeLog.lpfc | 419 and kernel complained about unlocking lock which is not locked.
|
