Lines Matching refs:we
10 When taking the i_rwsem on multiple non-directory objects, we
16 1) read access. Locking rules: caller locks directory we are accessing.
29 lock it. If we need to lock both, lock them in inode pointer order.
31 NB: we might get away with locking the source (and target in exchange
55 lock it. If we need to lock both, do so in inode pointer order.
58 All ->i_rwsem are taken exclusive. Again, we might get away with locking
69 First of all, at any moment we have a partial ordering of the
75 attempts to acquire lock on B, A will remain the parent of B until we
81 renames will be blocked on filesystem lock and we don't start changing
82 the order until we had acquired all locks).
111 would have a contended child and we had assumed that no object is its
116 of its descendents is locked by cross-directory rename (otherwise we
119 to (2) the order hadn't changed since we had acquired filesystem lock.
120 But locking rules for cross-directory rename guarantee that we do not
133 we had acquired filesystem lock and rename() would fail with -ELOOP in that
143 children", so if we are going to introduce hybrid objects we will need