Searched refs:unlocking (Results 1 – 21 of 21) sorted by relevance
| /Linux-v4.19/Documentation/devicetree/bindings/clock/ |
| D | arm-syscon-icst.txt | 49 unlocking register is located
|
| /Linux-v4.19/Documentation/locking/ |
| D | rt-mutex.txt | 40 locking overhead when locking an uncontended mutex or unlocking a mutex
|
| D | ww-mutex-design.txt | 277 /* need to do that before unlocking, since only the current lock holder is
366 unlocking all mutexes.
368 before unlocking all mutexes.
|
| D | rt-mutex-design.txt | 426 The wait_lock of the mutex is taken since the slow path of unlocking the
505 The unlocking of a mutex also has a fast path for those architectures with
508 take the slow path when unlocking the mutex. If the mutex doesn't have any
516 mutex. This synchronizes the locking and unlocking of the mutex.
|
| D | mutex-design.txt | 80 - Recursive locking/unlocking is not permitted.
|
| /Linux-v4.19/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
|
| D | memory-barriers.txt | 2541 issued prior to unlocking the critical section.
|
| /Linux-v4.19/fs/dlm/ |
| D | dlm_internal.h | 698 struct list_head unlocking; member
|
| D | user.c | 650 INIT_LIST_HEAD(&proc->unlocking); in device_open()
|
| D | lock.c | 6000 list_move(&lkb->lkb_ownqueue, &ua->proc->unlocking); in dlm_user_unlock()
6197 list_for_each_entry_safe(lkb, safe, &proc->unlocking, lkb_ownqueue) { in dlm_clear_proc_locks()
6237 list_for_each_entry_safe(lkb, safe, &proc->unlocking, lkb_ownqueue) { in purge_proc_locks()
|
| /Linux-v4.19/fs/jffs2/ |
| D | README.Locking | 55 lead to deadlock, unless we played games with unlocking the i_sem
|
| /Linux-v4.19/Documentation/filesystems/ |
| D | mandatory-locking.txt | 35 update, before applying its own lock, updating the file and unlocking it again.
|
| D | Locking | 281 followed by unlocking it. Once set_page_writeback() has been run against the
|
| D | porting | 38 typically between calling iget_locked() and unlocking the inode.
|
| D | vfs.txt | 283 unfreeze_fs: called when VFS is unlocking a filesystem and making it writable
737 The filesystem must take care of unlocking the page and releasing it
|
| D | fscrypt.rst | 165 requirement to support unlocking a file with multiple alternative
|
| /Linux-v4.19/Documentation/vm/ |
| D | unevictable-lru.rst | 422 zeros out the page_mapping of the old page before unlocking it, so m[un]lock
|
| /Linux-v4.19/Documentation/filesystems/caching/ |
| D | netfs-api.txt | 743 associated object before unlocking the cookie.
|
| /Linux-v4.19/Documentation/cdrom/ |
| D | cdrom-standard.tex | 369 However, strategic actions such as ejection of the tray, or unlocking
|
| /Linux-v4.19/Documentation/scsi/ |
| D | ChangeLog.lpfc | 419 and kernel complained about unlocking lock which is not locked.
|
