Searched refs:held (Results 1 – 25 of 107) sorted by relevance
12345
| /linux-3.4.99/Documentation/pcmcia/ |
| D | locking.txt | 17 be called with "skt_mutex" held:
34 be called with "ops_mutex" held:
43 called with "ops_mutex" held.
|
| /linux-3.4.99/Documentation/ |
| D | robust-futex-ABI.txt | 7 futexes, for kernel assist of cleanup of held locks on task exit.
16 held robust_futexes begins, and
17 2) internal kernel code at exit, to handle any listed locks held
83 For each futex lock currently held by a thread, if it wants this
112 up locks held at the time of (a perhaps unexpectedly) exit.
119 still held by the departing thread, as described below.
123 lock structures for locks currently held by that thread should be on
126 A given futex lock structure in a user shared memory region may be held
131 When adding or removing a lock from its list of held locks, in order for
|
| D | mutex-design.txt | 90 * - task may not exit with mutex held
91 * - memory areas where held locks reside must not be freed
92 * - held mutexes must not be reinitialized
101 * - list of all locks held in the system, printout of them
|
| D | lockstat.txt | 52 hold time min - shortest (non-0) time we ever held the lock
53 max - longest time we ever held the lock
54 total - total time this lock was held
|
| D | lockdep-design.txt | 32 - 'ever held in STATE context'
33 - 'ever held as readlock in STATE context'
34 - 'ever held with STATE enabled'
35 - 'ever held as readlock with STATE enabled'
108 any rule violation between the new lock and any of the held locks.
218 held locks is maintained, and a lightweight 64-bit hash value is
|
| D | robust-futexes.txt | 42 then the kernel has no information to clean up after the held lock!
148 million (!) held locks, using the new method [on a 2GHz CPU]:
158 (1 million held locks are unheard of - we expect at most a handful of
159 locks to be held at a time. Nevertheless it's nice to know that this
187 If a futex is found to be held at exit time, the kernel sets the
|
| D | rt-mutex.txt | 58 taskpointer 0 0 mutex is held (fast release possible)
60 taskpointer 1 0 mutex is held and has waiters
|
| D | volatile-considered-harmful.txt | 33 change unexpectedly while the_lock is held. Any other code which might
45 can be working with it. While the lock is held, shared_data is not
|
| /linux-3.4.99/Documentation/filesystems/nfs/ |
| D | pnfs.txt | 20 LAYOUTCOMMIT), and for each lseg held within.
30 layout driver type. The device ids are held in a RCU cache (struct
32 mount. The entries (struct nfs4_deviceid) themselves are held across
47 level cache. Its reference is held over the lifetime of the deviceid
|
| /linux-3.4.99/Documentation/filesystems/ |
| D | gfs2-glocks.txt | 18 held locks, then they will be contiguous entries at the head
83 Operation | GLF_LOCK bit lock held | gl_spin spinlock held
94 if its held on entry. go_dump and do_demote_ok must never block.
|
| D | porting | 98 without BKL held. BKL should have been shifted into individual fs sb_op
222 * the child's ->d_lock is held
254 ->statfs() is now called without BKL held. BKL should have been
303 inode->i_lock held and it returns true if filesystems wants the inode to be
429 You must also keep in mind that ->fsync() is not called with i_mutex held
|
| D | directory-locking | 73 Any contended object is either held by cross-directory rename or
74 has a child that is also contended. Indeed, suppose that it is held by
|
| /linux-3.4.99/Documentation/RCU/ |
| D | lockdep-splat.txt | 26 3 locks held by scsi_scan_6/1552:
80 or with the ->queue_lock held. In particular, this would have suppressed
81 the above lockdep-RCU splat because ->queue_lock is held (see #2 in the
|
| D | UP.txt | 69 2. In some cases, the lock will be held across some kernel API,
73 with no locks held than to have to modify such APIs to allow
87 from a known environment in which no locks are held.
|
| D | lockdep.txt | 82 2. with files->file_lock held, or
98 of these two cases held. Because rcu_dereference_protected() omits all
|
| /linux-3.4.99/Documentation/ABI/testing/ |
| D | sysfs-driver-hid-prodikeys | 16 note held by the pc-midi driver.
|
| /linux-3.4.99/Documentation/power/ |
| D | pm_qos_interface.txt | 29 aggregated target value is simply the max or min of the request values held
77 As long as the device node is held open that process has a registered
94 aggregated target value is simply the max or min of the request values held
|
| /linux-3.4.99/Documentation/vm/ |
| D | locking | 47 that invokes find_vma with mmap_sem held), but that is okay, since it
73 held.
107 Pages are added into the swap cache with kernel_lock held, to make sure
|
| /linux-3.4.99/drivers/block/paride/ |
| D | Transition-notes | 51 2) When there is such a thread, pd_busy is set or pd_lock is held by
54 held by that thread.
56 ->claim_cont or pi_spinlock is held by thread in question.
|
| /linux-3.4.99/fs/jffs2/ |
| D | README.Locking | 26 When writing new nodes, the alloc_sem must be held until the new nodes
69 any f->sem held.
133 erase_completion_lock cannot be held, so an alternative, more
|
| /linux-3.4.99/scripts/coccinelle/locks/ |
| D | mini_lock.cocci | 5 /// supposed to exit with the lock held, or where there is some preceding
|
| D | call_kern.cocci | 1 /// Find functions that refer to GFP_KERNEL but are called with locks held.
|
| /linux-3.4.99/Documentation/device-mapper/ |
| D | thin-provisioning.txt | 241 <used data blocks>/<total data blocks> <held metadata root>
254 held metadata root:
256 'held' for userspace read access. '-' indicates there is no
257 held root. This feature is not yet implemented so '-' is
|
| /linux-3.4.99/drivers/staging/iio/Documentation/ |
| D | ring.txt | 46 Get/set the number of complete scans that may be held by the buffer.
|
| /linux-3.4.99/Documentation/cgroups/ |
| D | cgroups.txt | 426 has processes attached, or is held alive by other subsystem-specific
562 (cgroup_mutex held by caller)
577 (cgroup_mutex held by caller)
596 (cgroup_mutex held by caller)
617 (cgroup_mutex held by caller)
626 (cgroup_mutex held by caller)
641 (cgroup_mutex held by caller)
651 (cgroup_mutex held by caller)
659 (cgroup_mutex and ss->hierarchy_mutex held by caller)
|
12345