Lines Matching refs:and

26 only be unique when combined with st_dev, and both of these can change
27 over the lifetime of a non-directory object.  Many applications and
28 tools ignore these values and will not be affected.
30 Upper and Lower
34 and a 'lower' filesystem.  When a name exists in both filesystems, the
39 It would be more correct to refer to an upper and lower 'directory
41 directory trees to be in the same filesystem and there is no
45 The lower filesystem can be any filesystem supported by Linux and does
47 overlayfs.  The upper filesystem will normally be writable and if it
48 is it must support the creation of trusted.* extended attributes, and
58 upper and lower filesystems and refers to a non-directory in either,
62 Where both upper and lower objects are directories, a merged directory
65 At mount time, the two directories given as mount options "lowerdir" and
75 lookup is performed in each actual directory and the combined result
77 actual lookups find directories, both are stored and a merged
82 such as metadata and extended attributes are reported for the upper
85 whiteouts and opaque directories
88 In order to support rm and rmdir without changing the lower
90 that files have been removed.  This is done using whiteouts and opaque
95 matching name in the lower level is ignored, and the whiteout itself
105 When a 'readdir' request is made on a merged directory, the upper and
106 lower directories are each read and the name lists merged in the
109 'struct file' and so remains as long as the file is kept open.  If the
110 directory is opened and read by two processes at the same time, they
113 discarded and rebuilt.
122   - remember an offset, and close the directory
126 there may be little correlation between the old and new locations in
150 exists in the upper filesystem - creating it and any parents as
152 mode, mtime, symlink-target etc.) and then if the object is a file, the
160 rename or unlink will of course be noticed and handled).
171 As the example shows, "upperdir=" and "workdir=" may be omitted.  In
175 rightmost one and going left.  In the above example lower1 will be the
176 top, lower2 the middle and lower3 the bottom layer.
182 The copy_up operation essentially creates a new, identical file and
184 filesystem, so both st_dev and st_ino of the file may change.
186 Any open files referring to this inode will access the old data and
190 On a file opened with O_RDONLY fchmod(2), fchown(2), futimesat(2) and
197 Symlinks in /proc/PID/ and /proc/PID/fd which point to a non-directory