Lines Matching refs:we

5 	When taking the i_mutex on multiple non-directory objects, we
11 1) read access.  Locking rules: caller locks directory we are accessing.
20 it.  If source is a non-directory, lock it.  If that means we need to
39 	  it.  In case that means we need to lock both source and target,
51 	First of all, at any moment we have a partial ordering of the
57     attempts to acquire lock on B, A will remain the parent of B until we
63     renames will be blocked on filesystem lock and we don't start changing
64     the order until we had acquired all locks).
93 would have a contended child and we had assumed that no object is its
98 of its descendents is locked by cross-directory rename (otherwise we
101 to (2) the order hadn't changed since we had acquired filesystem lock.
102 But locking rules for cross-directory rename guarantee that we do not
115 we had acquired filesystem lock and rename() would fail with -ELOOP in that
125 children", so if we are going to introduce hybrid objects we will need