Lines Matching refs:order

6 always acquire the locks in order by increasing address.  We'll call
7 that "inode pointer" order in the following.
21 lock both, lock them in inode pointer order.
32 	* lock parents in "ancestors first" order.
40 	  do so in inode pointer order.
61 (2) if cross-directory rename holds the lock on filesystem, order will not
64     the order until we had acquired all locks).
67     directory objects, and are acquired in inode pointer order.
70     target in inode pointer order in the case they are not directories.)
100 means that cross-directory rename is taking locks out of order.  Due
101 to (2) the order hadn't changed since we had acquired filesystem lock.