Lines Matching refs:locks

2 kinds of locks - per-inode (->i_mutex) and per-filesystem
6 always acquire the locks in order by increasing address.  We'll call
11 1) read access.  Locking rules: caller locks directory we are accessing.
15 3) object removal.  Locking rules: caller locks parent, finds victim,
16 locks victim and calls the method.
18 4) rename() that is _not_ cross-directory.  Locking rules: caller locks
62     change until rename acquires all locks.  (Proof: other cross-directory
64     the order until we had acquired all locks).
66 (3) locks on non-directory objects are acquired only after locks on
69     non-directory object, except renames, which take locks on source and
74 consider the set of contended locks.  First of all, filesystem lock is
75 not contended, since any process blocked on it is not holding any locks.
81 non-directory objects are not included in the set of contended locks.
84 blocked on source and it means that it doesn't hold any locks.
100 means that cross-directory rename is taking locks out of order.  Due