On Wed, Nov 29, 2017 at 4:54 PM, Vivek Goyal <vgoyal@xxxxxxxxxx> wrote: > Now we will have the capability to have upper inodes which might be only > metadata copy up and data is still on lower inode. So add a new xattr > OVL_XATTR_METACOPY to distinguish between two cases. Maybe I missed something, but I think there's a bug in this patch: truncate() is a metadata+data operation since it affects results of read(). So it should be handled by doing the data copy-up like we did before. 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
