Lines Matching refs:locks

7 kinds of locks - per-inode (->i_rwsem) and per-filesystem
11 always acquire the locks in order by increasing address.  We'll call
16 1) read access.  Locking rules: caller locks directory we are accessing.
22 3) object removal.  Locking rules: caller locks parent, finds victim,
23 locks victim and calls the method.  Locks are exclusive.
25 4) rename() that is _not_ cross-directory.  Locking rules: caller locks
30 Then call the method.  All locks are exclusive.
41 All locks are exclusive.
80     change until rename acquires all locks.  (Proof: other cross-directory
82     the order until we had acquired all locks).
84 (3) locks on non-directory objects are acquired only after locks on
87     non-directory object, except renames, which take locks on source and
92 consider the set of contended locks.  First of all, filesystem lock is
93 not contended, since any process blocked on it is not holding any locks.
99 non-directory objects are not included in the set of contended locks.
102 blocked on source and it means that it doesn't hold any locks.
118 means that cross-directory rename is taking locks out of order.  Due