On Mon, Apr 24, 2017 at 11:14 AM, Amir Goldstein <amir73il@xxxxxxxxx> wrote: > Sometimes it is interesting to know if an upper file is pure > upper or a copy up target, and if it is a copy up target, it > may be interesting to find the copy up origin. > > This will be used to preserve lower inode numbers across copy up. > > Store the lower inode file handle in upper inode xattr overlay.fh > on copy up to use it later for these cases. > > On failure to encode lower file handle, store an invalid 'null' > handle, so we can always use the overlay.fh xattr to distignuish > between a copy up and a pure upper inode. > > If lower fs does not support NFS export ops or if not all lower > layers are on the same fs, don't try to encode a lower file handle > and use the 'null' handle instead. One other question regarding this: do we want to store the handle of the next file in the copy up chain or the handle of the original file? This patch seems to do the "next file" thing. For directories, obviously that's what we want, but for files... Thanks, Miklos -- 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
