Lines Matching refs:directory

23 all non-directory objects will report an st_dev from the lower or
26 over the lifetime of a non-directory object.  Many applications and
38 It would be more correct to refer to an upper and lower 'directory
40 directory trees to be in the same filesystem and there is no
57 upper and lower filesystems and refers to a non-directory in either,
61 Where both upper and lower objects are directories, a merged directory
65 "upperdir" are combined into a merged directory:
70 The "workdir" needs to be an empty directory on the same filesystem
73 Then whenever a lookup is requested in such a merged directory, the
74 lookup is performed in each actual directory and the combined result
77 directory is created, otherwise only one is stored: the upper if it
82 directory only.  These attributes of the lower directory are hidden.
93 When a whiteout is found in the upper level of a merged directory, any
97 A directory is made opaque by setting the xattr "trusted.overlay.opaque"
98 to "y".  Where the upper filesystem contains an opaque directory, any
99 directory in the lower filesystem with the same name is ignored.
104 When a 'readdir' request is made on a merged directory, the upper and
109 directory is opened and read by two processes at the same time, they
111 directory (offset 0) followed by a readdir will cause the cache to be
114 This means that changes to the merged directory do not appear while a
115 directory is being read.  This is unlikely to be noticed by many
120   - read part of a directory
121   - remember an offset, and close the directory
122   - re-open the directory some time later
127 directory.
130 underlying directory (upper or lower).
148 The copy_up process first makes sure that the containing directory
166 separator character between the directory names.  For example:
196 Symlinks in /proc/PID/ and /proc/PID/fd which point to a non-directory