| /linux-6.15/Documentation/devicetree/bindings/clock/ |
| H A D | arm,syscon-icst.yaml | 85 description: Offset to the unlocking register for the oscillator
|
| /linux-6.15/Documentation/locking/ |
| H A D | rt-mutex.rst | 41 locking overhead when locking an uncontended mutex or unlocking a mutex
|
| H A 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.
|
| H A D | robust-futex-ABI.rst | 71 in the middle of a locking or unlocking operation.
116 Actual locking and unlocking, during normal operations, is handled
|
| H A D | futex-requeue-pi.rst | 21 rest to the natural wakeup inherent in unlocking the mutex
|
| H A 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.
|
| H A D | mutex-design.rst | 83 - Recursive locking/unlocking is not permitted.
|
| /linux-6.15/Documentation/filesystems/iomap/ |
| H A D | porting.rst | 39 allocating, instantiating, locking, and unlocking of folios.
|
| /linux-6.15/fs/dlm/ |
| H A D | dlm_internal.h | 720 struct list_head unlocking; member
|
| H A D | user.c | 657 INIT_LIST_HEAD(&proc->unlocking); in device_open()
|
| H A D | lock.c | 5985 list_move(&lkb->lkb_ownqueue, &ua->proc->unlocking); in dlm_user_unlock()
6189 list_for_each_entry_safe(lkb, safe, &proc->unlocking, lkb_ownqueue) { in dlm_clear_proc_locks()
6228 list_for_each_entry_safe(lkb, safe, &proc->unlocking, lkb_ownqueue) { in purge_proc_locks()
|
| /linux-6.15/fs/jffs2/ |
| H A D | README.Locking | 55 lead to deadlock, unless we played games with unlocking the i_sem
|
| /linux-6.15/drivers/platform/surface/ |
| H A D | Kconfig | 162 necessary) unlocking and opening the latch connecting both parts.
|
| /linux-6.15/Documentation/virt/kvm/x86/ |
| H A D | amd-memory-encryption.rst | 501 attest the measurement associated with its context before unlocking any
|
| /linux-6.15/Documentation/mm/ |
| H A D | process_addrs.rst | 78 suitable variant), unlocking it with a matching :c:func:`!mmap_read_unlock` when
91 suitable variant), unlocking it with a matching :c:func:`!mmap_write_unlock` when
|
| /linux-6.15/Documentation/filesystems/ |
| H A D | netfs_library.rst | 349 uptodate, unlocking them or dropping their refs - the helpers need to deal
|
| H A D | vfs.rst | 367 called when VFS is unlocking a filesystem and making it writable
371 called when VFS is unlocking a filesystem and making it writable
965 The filesystem must take care of unlocking the folio,
|
| H A D | locking.rst | 343 followed by unlocking it. Once set_page_writeback() has been run against the
|
| H A D | porting.rst | 44 typically between calling iget_locked() and unlocking the inode.
|
| H A D | fscrypt.rst | 253 there is no requirement to support unlocking a file with multiple
|
| /linux-6.15/Documentation/driver-api/media/ |
| H A D | v4l2-subdev.rst | 616 and unlocking the state after the call.
|
| /linux-6.15/Documentation/cdrom/ |
| H A D | cdrom-standard.rst | 345 However, strategic actions such as ejection of the tray, or unlocking
|
| /linux-6.15/Documentation/scsi/ |
| H A D | ChangeLog.lpfc | 419 and kernel complained about unlocking lock which is not locked.
|
| /linux-6.15/Documentation/filesystems/xfs/ |
| H A D | xfs-online-fsck-design.rst | 3513 - Prior to unlocking inodes to start the scan, online fsck must call
|