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
29 Take the locks that need to be taken, in inode pointer order if need
34 After the locks had been taken, call the method.  All locks are exclusive.
43 All locks are exclusive.
83     change until rename acquires all locks.  (Proof: other cross-directory
85     the order until we had acquired all locks).
87 (3) locks on non-directory objects are acquired only after locks on
90     non-directory object, except renames, which take locks on source and
95 consider the set of contended locks.  First of all, filesystem lock is
96 not contended, since any process blocked on it is not holding any locks.
102 non-directory objects are not included in the set of contended locks.
105 blocked on source and it means that it doesn't hold any locks.
121 means that cross-directory rename is taking locks out of order.  Due