On Tue, Apr 25, 2017 at 2:52 PM, Vivek Goyal <vgoyal@xxxxxxxxxx> wrote: > On Mon, Apr 24, 2017 at 12:14:05PM +0300, Amir Goldstein wrote: >> Miklos, >> >> Following your comments on the 'stable inodes' series from last week, >> this series fixes constant inode numbers for stat(2) with any layer >> configuration. >> >> For the case of all *lower* layers on same fs that supports NFS export, >> redirect by file handle will be used to optimize the lookup of the copy >> up origin of non-dir inode. >> >> For the case of *all* layers on same fs, overlayfs also gains: >> - Persistent inode numbers for directories >> - Correct results for du -x >> >> Consistcy of stat(2) st_ino with readdir(3) d_ino is NOT addressed by >> this series. It will be addressed for the 'samefs' configuration by the >> follow up 'stable inode' work, which is also going to address preserving >> hardlinks on copy up. > > Hi Amir, > > We need to update Documentation/filesystems/overlayfs.txt as well to > reflect new semantics of reporting st_dev and st_ino? > Of course need to! I'll do that. Thanks! -- To unsubscribe from this list: send the line "unsubscribe linux-unionfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
