• Vivek Goyal's avatar
    overlayfs: During copy up, first copy up data and then xattrs · 2424e1c7
    Vivek Goyal authored
    If a file with capability set (and hence security.capability xattr) is
    written kernel clears security.capability xattr. For overlay, during file
    copy up if xattrs are copied up first and then data is, copied up. This
    means data copy up will result in clearing of security.capability xattr
    file on lower has. And this can result into surprises. If a lower file has
    CAP_SETUID, then it should not be cleared over copy up (if nothing was
    actually written to file).
    This also creates problems with chown logic where it first copies up file
    and then tries to clear setuid bit. But by that time security.capability
    xattr is already gone (due to data copy up), and caller gets -ENODATA.
    This has been reported by Giuseppe here.
    Fix this by copying up data first and then metadta. This is a regression
    which has been introduced by my commit as part of metadata only copy up
    TODO: There will be some corner cases where a file is copied up metadata
    only and later data copy up happens and that will clear security.capability
    xattr. Something needs to be done about that too.
    Fixes: bd64e575 ("ovl: During copy up, first copy up metadata and then data")
    Cc: <stable@vger.kernel.org> # v4.19+
    Reported-by: default avatarGiuseppe Scrivano <gscrivan@redhat.com>
    Signed-off-by: default avatarVivek Goyal <vgoyal@redhat.com>
    Signed-off-by: default avatarMiklos Szeredi <mszeredi@redhat.com>
Last commit
Last update
Kconfig Loading commit data...
Makefile Loading commit data...
copy_up.c Loading commit data...
dir.c Loading commit data...
export.c Loading commit data...
file.c Loading commit data...
inode.c Loading commit data...
namei.c Loading commit data...
overlayfs.h Loading commit data...
ovl_entry.h Loading commit data...
readdir.c Loading commit data...
super.c Loading commit data...
util.c Loading commit data...