Home
last modified time | relevance | path

Searched refs:unlocking (Results 1 – 21 of 21) sorted by relevance

/linux/Documentation/locking/
H A Dww-mutex-design.rst281 /* need to do that before unlocking, since only the current lock holder is
375 unlocking all mutexes.
377 before unlocking all mutexes.
H A Drt-mutex.rst41 locking overhead when locking an uncontended mutex or unlocking a mutex
H A Drobust-futex-ABI.rst71 in the middle of a locking or unlocking operation.
116 Actual locking and unlocking, during normal operations, is handled
H A Drt-mutex-design.rst437 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.
H A Dfutex-requeue-pi.rst21 rest to the natural wakeup inherent in unlocking the mutex
H A Dmutex-design.rst83 - Recursive locking/unlocking is not permitted.
/linux/Documentation/filesystems/iomap/
H A Dporting.rst39 allocating, instantiating, locking, and unlocking of folios.
/linux/fs/dlm/
H A Ddlm_internal.h722 struct list_head unlocking; member
H A Duser.c657 INIT_LIST_HEAD(&proc->unlocking); in device_open()
H A Dlock.c5969 list_move(&lkb->lkb_ownqueue, &ua->proc->unlocking); in dlm_user_unlock()
6173 list_for_each_entry_safe(lkb, safe, &proc->unlocking, lkb_ownqueue) { in dlm_clear_proc_locks()
6212 list_for_each_entry_safe(lkb, safe, &proc->unlocking, lkb_ownqueue) { in purge_proc_locks()
/linux/fs/jffs2/
H A DREADME.Locking55 lead to deadlock, unless we played games with unlocking the i_sem
/linux/drivers/platform/surface/
H A DKconfig162 necessary) unlocking and opening the latch connecting both parts.
/linux/Documentation/filesystems/
H A Dnetfs_library.rst129 and folio unlocking is performed progressively (if appropriate). Once the
132 library to cause folio unlocking to happen earlier if possible.
817 Note: the filesystem must not deal with setting folios uptodate, unlocking
H A Dvfs.rst296 called when VFS is unlocking a filesystem and making it writable
300 called when VFS is unlocking a filesystem and making it writable
877 The filesystem must take care of unlocking the folio,
H A Dporting.rst44 typically between calling iget_locked() and unlocking the inode.
H A Dfscrypt.rst281 there is no requirement to support unlocking a file with multiple
/linux/Documentation/virt/kvm/x86/
H A Damd-memory-encryption.rst501 attest the measurement associated with its context before unlocking any
/linux/Documentation/driver-api/media/
H A Dv4l2-subdev.rst616 and unlocking the state after the call.
/linux/Documentation/cdrom/
H A Dcdrom-standard.rst344 However, strategic actions such as ejection of the tray, or unlocking
/linux/Documentation/scsi/
H A DChangeLog.lpfc419 and kernel complained about unlocking lock which is not locked.
/linux/Documentation/filesystems/xfs/
H A Dxfs-online-fsck-design.rst3386 - Prior to unlocking inodes to start the scan, online fsck must call