Lines Matching refs:so

10 child with the next element, and so on.
26 dentry that was looked up, so that may be used as the basis for walking the
35 (including dcache look-up) completely "store-free" (so, no locks, atomics, or
84 The hash lists are RCU protected, so list walking is not serialised with
95 read-only protection and no durability of results, so care must be taken when
120 dentry. So a seqlock is used to detect when a rename has occurred, and so the
144 pointers intact, so a concurrent list walker that is currently looking at
203 Inodes are also rcu freed, so the seqcount lookup dentry's inode may also be
261     | name:    "npiggin"  |   not necessarily invalid, so we need only keep a
279 section on the grandparent, so we have nothing left to stand on. In that case,
295 * synchronize_rcu is called when unregistering a filesystem, so we can
302   so we can load this tuple atomically, and also check whether any of its
307 * inode is also RCU protected so we can load d_inode and use the inode for
364 only when we have reached the target dentry, so the other statistics show where