| /linux-4.4.14/drivers/crypto/ccp/ |
| D | ccp-crypto-main.c | 91 struct ccp_crypto_cmd *held = NULL, *tmp; in ccp_crypto_cmd_complete() local
105 held = tmp; in ccp_crypto_cmd_complete()
133 return held; in ccp_crypto_cmd_complete()
139 struct ccp_crypto_cmd *held, *next, *backlog; in ccp_crypto_complete() local
158 held = ccp_crypto_cmd_complete(crypto_cmd, &backlog); in ccp_crypto_complete()
175 while (held) { in ccp_crypto_complete()
179 held->cmd->flags |= CCP_CMD_MAY_BACKLOG; in ccp_crypto_complete()
180 ret = ccp_enqueue_cmd(held->cmd); in ccp_crypto_complete()
185 ctx = crypto_tfm_ctx(held->req->tfm); in ccp_crypto_complete()
187 ret = ctx->complete(held->req, ret); in ccp_crypto_complete()
[all …]
|
| /linux-4.4.14/kernel/rcu/ |
| D | sync.c | 27 #define __INIT_HELD(func) .held = func,
37 int (*held)(void); member
68 RCU_LOCKDEP_WARN(!gp_ops[rsp->gp_type].held(), in rcu_sync_lockdep_assert()
|
| /linux-4.4.14/Documentation/ |
| D | sparse.txt | 57 locking. These annotations tell sparse when a lock is held, with
60 __must_hold - The specified lock is held on function entry and exit.
62 __acquires - The specified lock is held on function exit, but not entry.
64 __releases - The specified lock is held on function entry, but not exit.
66 If the function enters and exits without the lock held, acquiring and
|
| 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 | 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 | 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
|
| D | clk.txt | 245 The enable lock is a spinlock and is held across calls to the .enable,
250 The prepare lock is a mutex and is held across calls to all other operations.
|
| D | assoc_array.txt | 56 RCU readlock is being held by the iterator. Note, however, under these
64 RCU readlock is being held by the thread doing the look up.
314 modified, provided the RCU read lock is held. Under such circumstances,
335 modified, provided the RCU read lock is held.
|
| D | pi-futex.txt | 45 short-held locks: for example, a highprio audio playback thread is
|
| D | iostats.txt | 94 To avoid introducing performance bottlenecks, no locks are held while
|
| D | vgaarbiter.txt | 72 unlock all : release all locks on target held by this user (not
|
| D | kref.txt | 183 kfree() with the lock held in the example above (since it is kind of
|
| D | xillybus.txt | 292 filled buffers being sent) and a latency held fairly low for tails of data.
316 FPGA, so the transmission of up to one word may be held until it's fully
|
| D | sysrq.txt | 74 'd' - Shows all locks that are held.
|
| D | kernel-docs.txt | 374 is held, whether interrupts can occur or not while it is held...
|
| D | media-framework.txt | 356 operation must be done with the media_device graph_mutex held.
|
| D | kprobes.txt | 131 spinlock held, maxactive = 1 should be enough. If the function is
|
| D | memory-barriers.txt | 2253 (5) release the reference held on the waiter's task struct.
|
| /linux-4.4.14/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-4.4.14/Documentation/device-mapper/ |
| D | era.txt | 50 <current era> <held metadata root | '-'>
57 held metadata root : The location, in blocks, of the metadata root
58 that has been 'held' for userspace read
59 access. '-' indicates there is no held root
|
| D | thin-provisioning.txt | 276 <used data blocks>/<total data blocks> <held metadata root>
289 held metadata root:
291 'held' for userspace read access. '-' indicates there is no
292 held root.
|
| /linux-4.4.14/Documentation/leds/ |
| D | ledtrig-transient.txt | 11 features that require an on or off state to be held just once and then stay in
79 - state allows user to specify a transient state to be held for the specified
97 state - transient state to be held. It has two values 0 or 1. 0 maps
99 held for the duration of the one shot timer and then the
128 held for the specified duration.
130 held for the specified duration.
|
| /linux-4.4.14/Documentation/locking/ |
| D | lockstat.txt | 53 hold time min - shortest (non-0) time we ever held the lock
54 max - longest time we ever held the lock
55 total - total time this lock was held
56 avg - average 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 | rt-mutex.txt | 58 taskpointer 0 0 mutex is held (fast release possible)
60 taskpointer 1 0 mutex is held and has waiters
|
| D | mutex-design.txt | 96 - A task may not exit with a mutex held.
97 - Memory areas where held locks reside must not be freed.
109 list of all locks held in the system, printout of them.
|
| D | ww-mutex-design.txt | 217 held there's no need for additional book-keeping to break cycles in the graph
218 or keep track off which looks are already held (when using more than one node
|
| D | lglock.txt | 120 with a held lock [4] and that makes it very expensive. A discussion on
|
| D | rt-mutex-design.txt | 422 When this function is called, there are no locks held. That also means
508 In the code to release the lock, the wait_lock of the mutex is held
|
| /linux-4.4.14/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-4.4.14/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 | 77 2. with files->file_lock held, or
93 of these two cases held. Because rcu_dereference_protected() omits all
|
| D | listRCU.txt | 35 /* Note: audit_netlink_sem held by caller. */
59 /* Note: audit_netlink_sem held by caller. */
174 /* Note: audit_netlink_sem held by caller. */
|
| D | checklist.txt | 302 primitives when the update-side lock is held is that doing so
|
| /linux-4.4.14/Documentation/virtual/kvm/devices/ |
| D | vfio.txt | 12 VFIO-group is held by KVM.
|
| /linux-4.4.14/fs/jffs2/ |
| D | README.Locking | 22 When writing new nodes, the alloc_sem must be held until the new nodes
65 any f->sem held.
68 3. Never lock a page cache page with f->sem held.
130 erase_completion_lock cannot be held, so an alternative, more
|
| /linux-4.4.14/drivers/staging/rdma/ |
| D | Kconfig | 11 fall into one of two categories: deprecated drivers being held
|
| /linux-4.4.14/Documentation/ABI/testing/ |
| D | sysfs-driver-hid-prodikeys | 16 note held by the pc-midi driver.
|
| D | sysfs-class-fpga-manager | 27 * reset = FPGA held in reset state
|
| D | sysfs-block-bcache | 83 written to the cache and the cache held no dirty data for that
|
| /linux-4.4.14/arch/arm/common/ |
| D | vlock.S | 64 ldrb r2, [r0, #VLOCK_OWNER_OFFSET] @ check whether lock is held
|
| /linux-4.4.14/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-4.4.14/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-4.4.14/Documentation/cgroups/ |
| D | cgroups.txt | 421 has processes attached, or is held alive by other subsystem-specific
538 (cgroup_mutex held by caller)
553 (cgroup_mutex held by caller)
563 (cgroup_mutex held by caller)
573 (cgroup_mutex held by caller)
582 (cgroup_mutex held by caller)
603 (cgroup_mutex held by caller)
617 (cgroup_mutex held by caller)
626 (cgroup_mutex held by caller)
645 (cgroup_mutex held by caller)
|
| /linux-4.4.14/Documentation/filesystems/ |
| D | gfs2-glocks.txt | 18 held locks, then they will be contiguous entries at the head
85 Operation | GLF_LOCK bit lock held | gl_lockref.lock spinlock held
97 if its held on entry. go_dump and do_demote_ok must never block.
|
| D | porting | 221 * the child's ->d_lock is held
253 ->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
424 You must also keep in mind that ->fsync() is not called with i_mutex held
461 called with both ->i_lock and inode_hash_lock held; the former is *not*
463 of the in-tree instances did). inode_hash_lock is still held,
|
| D | directory-locking | 86 Any contended object is either held by cross-directory rename or
87 has a child that is also contended. Indeed, suppose that it is held by
|
| D | Locking | 352 to block. Leases however can still be freed while the i_lock is held and
375 *an* inode->i_lock held. It may not be the i_lock of the inode
379 For deadlock detection however, the blocked_lock_lock is also held. The
380 fact that these locks are held ensures that the file_locks do not
425 held.
|
| D | files.txt | 59 be held.
|
| D | vfs.txt | 235 All methods are called without any locks being held, unless otherwise
258 with the inode->i_lock spinlock held.
273 (i.e. unmount). This is called with the superblock lock held
289 with the kernel lock held
370 Again, all methods are called without any locks being held, unless
391 This method is called with the directory inode semaphore held
839 Again, all methods are called without any locks being held, unless
994 However, our vfsmount is pinned, and RCU held, so the dentries and
1020 held, d_dname() should not try to modify the dentry itself, unless
|
| D | xfs-delayed-logging-design.txt | 40 the aggregation of all the previous changes currently held only in the log.
171 flushing thread has the delayed logging tracking lock already held, and is
632 while we are holding out a CIL flush, so at the moment that means it is held
642 items, it will get held for a significant time and so spin contention is a
645 transaction commit or CIL flush side sleeps with the lock held.
657 held for a very short time and so a spin lock is appropriate here. It is
|
| D | qnx6.txt | 78 the data held in the object and all of the metadata about an object except
|
| D | mandatory-locking.txt | 18 lock was held.
|
| D | autofs4-mount-control.txt | 106 on the mount point for control operations. The references held by the
108 in use and is also used to access autofs file system information held
|
| D | coda.txt | 502 u_quad_t va_bytes; /* bytes of disk space held by file */
723 will depend on whether a _t_o_k_e_n is held by the user.
1481 is to prevent stale cache information being held. Some operating
1659 6. All memory held by cnodes can be freed without relying on upcalls.
|
| D | ext2.txt | 138 data held in the object and all of the metadata about an object except
|
| D | proc.txt | 138 mem Memory held by this process
|
| /linux-4.4.14/Documentation/hwmon/ |
| D | nct6683 | 35 firmware is held under NDA by Nuvoton and Intel and not available
|
| D | pc87360 | 121 channels). For technical reasons, these channels are held by the VLM
|
| /linux-4.4.14/drivers/staging/iio/Documentation/ |
| D | ring.txt | 46 Set the number of complete scans that may be held by the buffer.
|
| /linux-4.4.14/Documentation/virtual/kvm/ |
| D | locking.txt | 64 - We have held the refcount of pfn that means the pfn can not be freed and
164 Comment: The srcu read lock must be held while accessing memslots (e.g.
|
| /linux-4.4.14/Documentation/powerpc/ |
| D | firmware-assisted-dump.txt | 34 -- Once the dump is copied out, the memory that held the dump
104 memory is held.
203 region that are held for saving crash dump. To release the
|
| D | cxlflash.txt | 309 at which time the context/resources they held will be freed as part of
|
| D | hvcs.txt | 467 Power5 systems to determine the many ways a system console can be held.
|
| /linux-4.4.14/Documentation/power/ |
| D | pm_qos_interface.txt | 31 aggregated target value is simply the max or min of the request values held
79 As long as the device node is held open that process has a registered
99 simply the minimum of the request values held in the parameter list elements.
|
| D | notifiers.txt | 50 The hibernation and suspend notifiers are called with pm_mutex held. They are
|
| D | runtime_pm.txt | 277 will be invoked with the spinlock held and interrupts disabled
|
| /linux-4.4.14/Documentation/scsi/ |
| D | scsi_mid_low_api.txt | 794 * Locks: none held
821 * Locks: None held
841 * Locks: None held
862 * Locks: None held
880 * Locks: None held
898 * Locks: None held
991 * Locks: none held
1050 * held on entry (with "irqsave") and is expected to be
1051 * held on return. From 2.6.37 onwards, queuecommand is
1052 * called without any locks held.
[all …]
|
| D | scsi_fc_transport.txt | 458 * This routine assumes no locks are held on entry.
471 * This routine assumes no locks are held on entry.
|
| D | ChangeLog.lpfc | 223 still is called with the lock held.
418 * Functions which assume lock being held were called without lock
683 the host_lock held.
703 resources without a lock held. Revert to msleep. Tested with
1406 lock was not held, but needed to be (in lpfc_linux_attach) Fixed
1420 lock since it expects this lock to be held.
|
| D | LICENSE.qla4xxx | 221 If any portion of this section is held invalid or unenforceable under
|
| D | LICENSE.qla2xxx | 222 If any portion of this section is held invalid or unenforceable under
|
| D | ChangeLog.megaraid | 243 asserting that it must be held (maybe just for
|
| /linux-4.4.14/Documentation/driver-model/ |
| D | bus.txt | 82 lock is not held when calling the callback.
|
| /linux-4.4.14/Documentation/video4linux/cx2341x/ |
| D | fw-memory.txt | 21 address held in BAR0.
|
| /linux-4.4.14/Documentation/video4linux/ |
| D | radiotrack.txt | 100 0 : Tuner held constant
|
| D | v4l2-controls.txt | 365 by the same handler since the handler's lock is held. If you need to access
748 v4l2_ctrl_notify. Note that the control's handler lock is held when the
|
| D | videobuf | 104 held; if it tries to acquire it as well things will come to a screeching
|
| /linux-4.4.14/Documentation/networking/ |
| D | x25-iface.txt | 15 All messages are held in sk_buff's just like real data to be transmitted
|
| D | netdev-features.txt | 58 ndo_*_features callbacks are called with rtnl_lock held. Missing callbacks
|
| D | cxgb.txt | 103 and is done at "YOUR OWN RISK". Chelsio will not be held responsible for loss
|
| D | LICENSE.qlcnic | 220 If any portion of this section is held invalid or unenforceable under
|
| D | LICENSE.qlge | 220 If any portion of this section is held invalid or unenforceable under
|
| D | ip-sysctl.txt | 348 held by system. If this number is exceeded orphaned connections are
366 Maximal number of timewait sockets held by system simultaneously.
|
| /linux-4.4.14/Documentation/s390/ |
| D | cds.txt | 335 ccw_device_start() must be called disabled and with the ccw device lock held.
413 ccw_device_halt() must be called disabled and with the ccw device lock held.
446 ccw_device_clear() must be called disabled and with the ccw device lock held.
|
| /linux-4.4.14/Documentation/isdn/ |
| D | README.diversion | 68 is selected the call will be held in a proceeding state (without ringing)
|
| D | INTERFACE | 526 4 = Call will be held in a proceeding state
|
| /linux-4.4.14/Documentation/security/ |
| D | keys.txt | 1074 RCU must be used when the semaphore isn't already held; if the semaphore
1075 is held then the contents can't change under you unexpectedly as the
1093 payload just dereferenced if the key's semaphore is not held.
1274 locks will be held over it.
1313 This method will be called with the RCU read lock held. rcu_dereference()
1320 It is not safe to sleep in this method; the RCU read lock is held by the
1401 hand the request off to (perhaps a path held in placed in another key by, for
|
| D | credentials.txt | 277 In Linux, all of a task's credentials are held in (uid, gid) or through
468 held if successful. It returns NULL if not successful (out of memory).
|
| /linux-4.4.14/Documentation/input/ |
| D | iforce-protocol.txt | 10 I shall not be held responsible for any damage or harm caused if you try to
|
| D | input-programming.txt | 103 not be called from an interrupt or with a spinlock held.
|
| /linux-4.4.14/Documentation/filesystems/caching/ |
| D | backend-api.txt | 220 performed on the denizens of the cache. These are held in a structure of type:
289 to schedule with the lock held, so a spinlock isn't sufficient.
340 This method should not attempt to release any references held by the
|
| D | object.txt | 187 to be read out of the cache for that file that isn't currently also held
|
| D | netfs-api.txt | 865 This can be called with spinlocks held as it defers the work to a thread pool.
|
| /linux-4.4.14/Documentation/arm/Samsung-S3C24XX/ |
| D | Overview.txt | 48 Register, kernel and platform data definitions are held in the
|
| /linux-4.4.14/Documentation/scheduler/ |
| D | completion.txt | 140 time, you probably don't want to call this with held mutexes.
|
| /linux-4.4.14/fs/ceph/ |
| D | caps.c | 1116 int held, revoking, dropping, keep; in __send_cap() local
1131 held = cap->issued | cap->implemented; in __send_cap()
1138 ceph_cap_string(held), ceph_cap_string(held & retain), in __send_cap()
|
| /linux-4.4.14/Documentation/DocBook/ |
| D | device-drivers.xml.db | 250 API-rcu-read-lock-sched-held
253 API-rcu-read-lock-held
254 API-rcu-read-lock-bh-held
|
| /linux-4.4.14/Documentation/trace/ |
| D | ring-buffer-design.txt | 91 The ring buffer is made up of a list of pages held together by a linked list.
173 if what is in the ring buffer is less than what is held in a buffer page.
|
| /linux-4.4.14/fs/btrfs/ |
| D | ctree.c | 79 struct extent_buffer *held, int held_rw) in btrfs_clear_path_blocking() argument
83 if (held) { in btrfs_clear_path_blocking()
84 btrfs_set_lock_blocking_rw(held, held_rw); in btrfs_clear_path_blocking()
102 if (held) in btrfs_clear_path_blocking()
103 btrfs_clear_lock_blocking_rw(held, held_rw); in btrfs_clear_path_blocking()
|
| D | ctree.h | 3654 struct extent_buffer *held, int held_rw);
|
| /linux-4.4.14/Documentation/usb/ |
| D | URB.txt | 179 completion handler, the handler must not take any lock that is held
|
| D | power-management.txt | 475 autoresume -- the device semaphore (udev->dev.sem) will be held when a
|
| /linux-4.4.14/Documentation/cpu-freq/ |
| D | governors.txt | 263 per-CPU cpufreq lock is still held in the cpufreq core, and there's
|
| /linux-4.4.14/arch/m68k/ |
| D | Kconfig.cpu | 378 Copyback caching means that memory writes will be held in an on-chip
|
| /linux-4.4.14/Documentation/crypto/ |
| D | asymmetric-keys.txt | 40 key, or it may interpret it as a reference to a key held somewhere else in the
|
| /linux-4.4.14/Documentation/vm/ |
| D | numa_memory_policy.txt | 304 to '1', representing the reference held by the task that is installing the
339 policy requires that the mmap_sem be held for write, the policy can't be
|
| D | unevictable-lru.txt | 432 A page that is being migrated has been isolated from the LRU lists and is held
448 page on failure - will be freed when the reference count held by the migration
|
| D | frontswap.txt | 235 capability of holding every page that the swap device might have held
|
| /linux-4.4.14/Documentation/serial/ |
| D | tty.txt | 232 point then NULL is returned. While this handle is held the ldisc will not
|
| D | driver | 394 Locking: port->lock should be held.
|
| /linux-4.4.14/lib/ |
| D | Kconfig.debug | 773 enabled then all held locks will also be reported. This
970 This feature will check whether any held lock (spinlock, rwlock,
975 held during task exit.
1064 held, inside an rcu read side critical section, inside preempt disabled
|
| /linux-4.4.14/drivers/staging/rtl8192u/ |
| D | copying | 210 If any portion of this section is held invalid or unenforceable under
|
| /linux-4.4.14/tools/usb/usbip/ |
| D | COPYING | 210 If any portion of this section is held invalid or unenforceable under
|
| /linux-4.4.14/drivers/staging/rtl8192e/ |
| D | license | 212 If any portion of this section is held invalid or unenforceable under any
|
| /linux-4.4.14/ |
| D | COPYING | 226 If any portion of this section is held invalid or unenforceable under
|
| /linux-4.4.14/drivers/char/ |
| D | Kconfig | 210 button; it will still execute a hard reset if the button is held
|
| /linux-4.4.14/Documentation/PCI/ |
| D | MSI-HOWTO.txt | 502 must disable interrupts while the lock is held. If the device sends
|
| /linux-4.4.14/Documentation/filesystems/cifs/ |
| D | README | 452 if oplock (caching token) is granted and held. Note that
|
| D | CHANGES | 604 break to self while vfs_unlink held i_sem) which can hang for 20 seconds.
|
| /linux-4.4.14/drivers/scsi/aic7xxx/ |
| D | aic79xx.seq | 2160 * CTXTDONE may be held off if a NONPACKREQ is associated with
|
| /linux-4.4.14/Documentation/virtual/uml/ |
| D | UserModeLinux-HOWTO.txt | 2445 after you send the 'stop' command, as only one CPU will be held in a
|