Home
last modified time | relevance | path

Searched full:unlocking (Results 1 – 25 of 144) sorted by relevance

123456

/linux/Documentation/locking/
H A Dww-mutex-design.rst223 Unlocking works the same way for both methods #1 and #2::
281 /* need to do that before unlocking, since only the current lock holder is
375 unlocking all mutexes.
377 before unlocking all mutexes.
381 - Unlocking mutexes with the wrong unlock function.
H A Drt-mutex-design.rst437 The wait_lock of the mutex is taken since the slow path of unlocking the
514 Unlocking the Mutex
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 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.rst41 locking overhead when locking an uncontended mutex or unlocking a 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/tools/testing/selftests/net/forwarding/
H A Dbridge_locked_port.sh116 check_err $? "Ping did not work after unlocking port and removing FDB entry."
146 check_err $? "Ping through vlan did not work after unlocking port and removing FDB entry"
174 check_err $? "Ping6 did not work after unlocking port and removing FDB entry"
/linux/arch/arm/include/asm/
H A Dspinlock.h135 * Write locks are easy - we just set bit 31. When unlocking, we can
203 * Unlocking is similarly hairy. We may have multiple read locks
/linux/Documentation/devicetree/bindings/clock/
H A Darm,syscon-icst.yaml85 description: Offset to the unlocking register for the oscillator
/linux/fs/ocfs2/
H A Dlocks.c50 * atomic, so we can get away with simply unlocking in ocfs2_do_flock()
/linux/drivers/power/reset/
H A Darm-versatile-reboot.c20 /* Magic unlocking token used on all Versatile boards */
/linux/kernel/locking/
H A Dmcs_spinlock.h34 * unlocking.
/linux/tools/testing/selftests/drivers/net/mlxsw/
H A Ddevlink_trap_l2_drops.sh463 check_fail $? "Trap stats increased after unlocking port"
504 check_fail $? "Trap stats increased after unlocking port"
/linux/include/linux/
H A Dww_mutex.h240 * acquired it. The task may not exit without first unlocking the mutex. Also,
272 * acquired it. The task may not exit without first unlocking the mutex. Also,
/linux/drivers/md/dm-vdo/
H A Ddedupe.c48 * lock on the duplicate block (UNLOCKING), and if the agent is the last data_vio referencing the
56 * -> QUERYING -> LOCKING -> VERIFYING -> DEDUPING -> UNLOCKING ->
58 * -> QUERYING -> LOCKING -> VERIFYING -> UNLOCKING -> WRITING -> UPDATING ->
212 [VDO_HASH_LOCK_UNLOCKING] = "UNLOCKING",
641 * UNLOCKING -> WRITING transition: The lock we released was on an unverified in finish_unlocking()
658 * UNLOCKING -> LOCKING transition: A new data_vio entered the hash lock while the in finish_unlocking()
671 * UNLOCKING -> BYPASSING transition: The agent is done with the lock and no other in finish_unlocking()
769 * UPDATING -> UNLOCKING transition: No one is waiting to dedupe, but we hold a in finish_updating()
841 * DEDUPING -> UNLOCKING transition: Release the PBN read lock on the duplicate in finish_deduping()
1113 * VERIFYING -> UNLOCKING transition: Either the verify failed or we'd try to in finish_verifying()
[all …]
/linux/Documentation/filesystems/iomap/
H A Dporting.rst39 allocating, instantiating, locking, and unlocking of folios.
/linux/include/uapi/linux/
H A Dfutex.h163 * has exited without unlocking the futex. The kernel also does
/linux/Documentation/driver-api/nvdimm/
H A Dsecurity.rst58 4. Unlocking
/linux/fs/jffs2/
H A DREADME.Locking55 lead to deadlock, unless we played games with unlocking the i_sem
/linux/drivers/mtd/spi-nor/
H A Dsst.c25 /* We only support unlocking the entire flash array. */ in sst26vf_nor_unlock()
/linux/block/partitions/
H A Dcore.c595 * beyond EOD, retry after unlocking the native capacity. in blk_add_partitions()
617 * If we read beyond EOD, try unlocking native capacity even if the in blk_add_partitions()
/linux/drivers/acpi/pmic/
H A Dintel_pmic_bytcrc.c257 /* Update to policy enable bit requires unlocking a0lock */ in intel_crc_pmic_update_policy()
/linux/Documentation/devicetree/bindings/mfd/
H A Dadi,adp5585.yaml73 means any key can be used for unlocking.
/linux/drivers/platform/surface/
H A DKconfig162 necessary) unlocking and opening the latch connecting both parts.
/linux/fs/xfs/
H A Dxfs_symlink.c178 * the transaction cancel unlocking dp so don't do it explicitly in the in xfs_symlink()

123456