On Wed, Aug 16, 2017 at 12:19 PM, Miklos Szeredi <miklos@xxxxxxxxxx> wrote: > On Tue, Aug 15, 2017 at 6:16 PM, Amir Goldstein <amir73il@xxxxxxxxx> wrote: >> On Tue, Aug 15, 2017 at 5:56 PM, Vivek Goyal <vgoyal@xxxxxxxxxx> wrote: > >>> IIUC, so now "chattr -p <id>" will fail on overlayfs (assume file has not >>> been copied up yet). >>> >> >> Yap. >> >>> IOW, on overlayfs, will it be responsibility of user space to make >>> sure file has been copied up, for chattr operation to succeed? Does that >>> mean we need to modify chattr to open file for WRITE instead of READ. >>> >> >> I guess that would make sense. >> I only wonder what was the reason for chattr to open RDONLY in >> the first place (cc Ted)?? > > What about copy up of flags? Should we? Does reflink copy the flags? That last one is a stupid question, reflink is a data copying operation, not an inode copying one... 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
