Searched refs:rename_lock (Results 1 – 9 of 9) sorted by relevance
/linux/fs/ |
H A D | d_path.c | 148 * It only checks the sequence number of the global rename_lock as any change 149 * in the dentry's d_seq will be preceded by changes in the rename_lock 151 * the whole pathname back-tracing sequence again by taking the rename_lock. 171 read_seqbegin_or_lock(&rename_lock, &seq); in prepend_path() 175 if (need_seqretry(&rename_lock, seq)) { in prepend_path() 179 done_seqretry(&rename_lock, seq); in prepend_path() 341 read_seqbegin_or_lock(&rename_lock, &seq); in __dentry_path() 352 if (need_seqretry(&rename_lock, seq)) { in __dentry_path() 356 done_seqretry(&rename_lock, seq); in __dentry_path()
|
H A D | dcache.c | 74 * arbitrary, since it's serialized on rename_lock 85 __cacheline_aligned_in_smp DEFINE_SEQLOCK(rename_lock); 87 EXPORT_SYMBOL(rename_lock); 1297 read_seqbegin_or_lock(&rename_lock, &seq); in d_walk() 1358 if (need_seqretry(&rename_lock, seq)) in d_walk() 1369 if (need_seqretry(&rename_lock, seq)) in d_walk() 1375 done_seqretry(&rename_lock, seq); in d_walk() 1433 * this reason take rename_lock and d_lock on dentry and ancestors. 1439 read_seqlock_excl(&rename_lock); in d_set_mounted() 1459 read_sequnlock_excl(&rename_lock); in d_set_mounted() [all...] |
H A D | namei.c | 2105 if (__read_seqcount_retry(&rename_lock.seqcount, nd->r_seq)) in handle_dots() 2538 nd->r_seq = __read_seqcount_begin(&rename_lock.seqcount); in path_init()
|
/linux/fs/nfs/ |
H A D | namespace.c | 69 seq = read_seqbegin(&rename_lock); in nfs_path() 85 if (read_seqretry(&rename_lock, seq)) { in nfs_path() 126 if (read_seqretry(&rename_lock, seq)) in nfs_path()
|
/linux/Documentation/filesystems/ |
H A D | path-lookup.rst | 217 rename_lock subsection 234 ``rename_lock`` is a seqlock that is updated whenever any dentry is 239 ``rename_lock`` is also used to detect and defend against potential attacks 242 check). If ``rename_lock`` is updated during the lookup and the path encounters 340 ``mount_lock`` is a global seqlock, a bit like ``rename_lock``. It can be used to 806 No ``inode->i_rwsem`` or even ``rename_lock`` 818 Though ``rename_lock`` could be used by RCU-walk as it doesn't require 819 any sleeping, RCU-walk doesn't bother. REF-walk uses ``rename_lock`` to 826 rename_lock would bring no significant value. 924 again - repeatedly". This is seen with the use of ``rename_lock`` an [all...] |
H A D | locking.rst | 40 ops rename_lock ->d_lock may block rcu-walk
|
/linux/fs/ocfs2/ |
H A D | namei.c | 1211 int status = 0, rename_lock = 0, parents_locked = 0, target_exists = 0; in ocfs2_rename() local 1279 rename_lock = 1; in ocfs2_rename() 1682 if (rename_lock) in ocfs2_rename()
|
/linux/kernel/ |
H A D | auditsc.c | 2126 seq = read_seqbegin(&rename_lock); in handle_path() 2146 if (unlikely(read_seqretry(&rename_lock, seq) || drop)) { /* in this order */ in handle_path()
|
/linux/fs/ceph/ |
H A D | mds_client.c | 2723 seq = read_seqbegin(&rename_lock); in ceph_mdsc_build_path() 2801 if (read_seqretry(&rename_lock, seq)) in ceph_mdsc_build_path()
|