Lines Matching refs:rename_lock

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
807 No ``inode->i_rwsem`` or even ``rename_lock``
819 Though ``rename_lock`` could be used by RCU-walk as it doesn't require
820 any sleeping, RCU-walk doesn't bother.  REF-walk uses ``rename_lock`` to
827 rename_lock would bring no significant value.
925 again - repeatedly".  This is seen with the use of ``rename_lock`` and
1364 ``rename_lock`` and ``mount_lock`` are used to detect attacks against the
1370 ``LOOKUP_BENEATH``, ``rename_lock`` and ``mount_lock`` are used to detect