Lines Matching full:order

11 always acquire the locks in order by increasing address.  We'll call
12 that "inode pointer" order in the following.
29 lock it.  If we need to lock both, lock them in inode pointer order.
47 	* lock parents in "ancestors first" order.
55 	  lock it.  If we need to lock both, do so in inode pointer order.
79 (2) if cross-directory rename holds the lock on filesystem, order will not
82     the order until we had acquired all locks).
85     directory objects, and are acquired in inode pointer order.
88     target in inode pointer order in the case they are not directories.)
118 means that cross-directory rename is taking locks out of order.  Due
119 to (2) the order hadn't changed since we had acquired filesystem lock.