| /OK3568_Linux_fs/yocto/meta-openembedded/meta-oe/recipes-extended/vlock/vlock-2.2.3/ |
| H A D | vlock-no_tally.patch | 67 +# unlocking?
|
| /OK3568_Linux_fs/kernel/Documentation/locking/ |
| 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 | rt-mutex.rst | 41 locking overhead when locking an uncontended mutex or unlocking a mutex
|
| 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 | 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 | futex-requeue-pi.rst | 21 rest to the natural wakeup inherent in unlocking the mutex
|
| H A D | mutex-design.rst | 83 - Recursive locking/unlocking is not permitted.
|
| /OK3568_Linux_fs/kernel/fs/dlm/ |
| H A D | dlm_internal.h | 695 struct list_head unlocking; member
|
| H A D | user.c | 648 INIT_LIST_HEAD(&proc->unlocking); in device_open()
|
| H A D | lock.c | 6018 list_move(&lkb->lkb_ownqueue, &ua->proc->unlocking); in dlm_user_unlock()
6215 list_for_each_entry_safe(lkb, safe, &proc->unlocking, lkb_ownqueue) { in dlm_clear_proc_locks()
6255 list_for_each_entry_safe(lkb, safe, &proc->unlocking, lkb_ownqueue) { in purge_proc_locks()
|
| /OK3568_Linux_fs/kernel/fs/jffs2/ |
| H A D | README.Locking | 55 lead to deadlock, unless we played games with unlocking the i_sem
|
| /OK3568_Linux_fs/kernel/Documentation/filesystems/ |
| H A D | mandatory-locking.rst | 40 update, before applying its own lock, updating the file and unlocking it again.
|
| H A D | locking.rst | 336 followed by unlocking it. Once set_page_writeback() has been run against the
|
| H A D | vfs.rst | 311 called when VFS is unlocking a filesystem and making it writable
837 The filesystem must take care of unlocking the page and
|
| H A D | porting.rst | 44 typically between calling iget_locked() and unlocking the inode.
|
| H A D | fscrypt.rst | 254 there is no requirement to support unlocking a file with multiple
|
| /OK3568_Linux_fs/kernel/Documentation/filesystems/caching/ |
| H A D | netfs-api.rst | 734 associated object before unlocking the cookie.
|
| /OK3568_Linux_fs/kernel/Documentation/vm/ |
| H A D | unevictable-lru.rst | 426 zeros out the page_mapping of the old page before unlocking it, so m[un]lock
|
| /OK3568_Linux_fs/kernel/Documentation/cdrom/ |
| H A D | cdrom-standard.rst | 346 However, strategic actions such as ejection of the tray, or unlocking
|
| /OK3568_Linux_fs/yocto/meta-openembedded/meta-oe/recipes-extended/polkit/polkit/ |
| H A D | 0003-Added-support-for-duktape-as-JS-engine.patch | 2176 + "Error unlocking mutex: %s",
|
| /OK3568_Linux_fs/kernel/Documentation/scsi/ |
| H A D | ChangeLog.lpfc | 419 and kernel complained about unlocking lock which is not locked.
|
| /OK3568_Linux_fs/prebuilts/gcc/linux-x86/aarch64/gcc-arm-10.3-2021.07-x86_64-aarch64-none-linux-gnu/aarch64-none-linux-gnu/libc/usr/share/info/ |
| H A D | libc.info-8 | 3875 be opened after unlocking, so portable applications should always
|
| H A D | libc.info-11 | 6759 or unlocking locks in shared data bases.
|
| /OK3568_Linux_fs/prebuilts/gcc/linux-x86/arm/gcc-arm-10.3-2021.07-x86_64-arm-none-linux-gnueabihf/arm-none-linux-gnueabihf/libc/usr/share/info/ |
| H A D | libc.info-8 | 3875 be opened after unlocking, so portable applications should always
|
| H A D | libc.info-11 | 6759 or unlocking locks in shared data bases.
|