Lines Matching refs:and

25 only be unique when combined with st_dev, and both of these can change
26 over the lifetime of a non-directory object.  Many applications and
27 tools ignore these values and will not be affected.
29 Upper and Lower
33 and a 'lower' filesystem.  When a name exists in both filesystems, the
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
44 The lower filesystem can be any filesystem supported by Linux and does
46 overlayfs.  The upper filesystem will normally be writable and if it
47 is it must support the creation of trusted.* extended attributes, and
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
64 At mount time, the two directories given as mount options "lowerdir" and
74 lookup is performed in each actual directory and the combined result
76 actual lookups find directories, both are stored and a merged
81 such as metadata and extended attributes are reported for the upper
84 whiteouts and opaque directories
87 In order to support rm and rmdir without changing the lower
89 that files have been removed.  This is done using whiteouts and opaque
94 matching name in the lower level is ignored, and the whiteout itself
104 When a 'readdir' request is made on a merged directory, the upper and
105 lower directories are each read and the name lists merged in the
108 'struct file' and so remains as long as the file is kept open.  If the
109 directory is opened and read by two processes at the same time, they
112 discarded and rebuilt.
121   - remember an offset, and close the directory
125 there may be little correlation between the old and new locations in
149 exists in the upper filesystem - creating it and any parents as
151 mode, mtime, symlink-target etc.) and then if the object is a file, the
159 rename or unlink will of course be noticed and handled).
170 As the example shows, "upperdir=" and "workdir=" may be omitted.  In
174 rightmost one and going left.  In the above example lower1 will be the
175 top, lower2 the middle and lower3 the bottom layer.
181 The copy_up operation essentially creates a new, identical file and
183 filesystem, so both st_dev and st_ino of the file may change.
185 Any open files referring to this inode will access the old data and
189 On a file opened with O_RDONLY fchmod(2), fchown(2), futimesat(2) and
196 Symlinks in /proc/PID/ and /proc/PID/fd which point to a non-directory