Lines Matching full:cross

40 5. rename that is _not_ cross-directory.  Locking rules:
53 6. cross-directory rename.  The trickiest in the whole bunch.  Locking rules:
110 step in cross-directory renames; we need to be careful when checking if
189 cross-directory rename of some sort.
191 There must be a cross-directory rename in the set; indeed,
200 more than one cross-directory rename among them.  Without loss of
201 generality we can assume that T1 is the one doing a cross-directory
204 In other words, we have a cross-directory rename that locked
208 cross-directory rename does not get to locking any directories until it
214 cross-directory rename; parents first, then possibly their children.
239 Note that the check for having a common ancestor in cross-directory
244 descendent of the parent of target.   At that point we have cross-directory
254 the only operation that could introduce loops is cross-directory rename.
280 also preserved by all operations (cross-directory rename on a tree that would