Lines Matching full:all

18 For our purposes all operations fall in 6 classes:
65 The rules above obviously guarantee that all directories that are going
95 First of all, we verify that it is *not* an ancestor of our directory
102 all we change is the view in dcache.  Moreover, holding a directory locked
120 using a local one as a cache, etc.  In all such cases the operations
137 There is a ranking on the locks, such that all primitives take
142   * put ->i_rwsem of all directories on a filesystem at the same rank,
152   2. ->i_rwsem of directories on that NFS filesystem, same rank for all
156   5. ->i_rwsem of directories on the local filesystem, same rank for all
167 Since the locking order is consistent with the ranking, all
169 i.e. they all will be ->i_rwsem of directories on the same filesystem.
170 Moreover, without loss of generality we can assume that all operations
192 if all operations had been of the "lock parent, then child" sort
196 so they would all hold simultaneously at the deadlock time and
199 Since all operations are on the same filesystem, there can't be
207 D1,...,Dn all hold simultaneously at the deadlock time.  Moreover,
211 all of them had been stable.
246 distant ancestor.  Add a bunch of rmdir() attempts on all directories
247 in between (all of those would fail with -ENOTEMPTY, had they ever gotten
280 also preserved by all operations (cross-directory rename on a tree that would