aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorVivek Goyal <vgoyal@redhat.com>2019-01-11 13:37:00 -0500
committerMiklos Szeredi <mszeredi@redhat.com>2019-02-04 03:09:57 -0500
commit5f32879ea35523b9842bdbdc0065e13635caada2 (patch)
treee7b689d9ac33aec212756ddd498ec6661646fbf1
parentbfeffd155283772bbe78c6a05dec7c0128ee500c (diff)
ovl: During copy up, first copy up data and then xattrs
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. https://github.com/containers/libpod/issues/2015#issuecomment-447824842 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 patches. 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: bd64e57586d3 ("ovl: During copy up, first copy up metadata and then data") Cc: <stable@vger.kernel.org> # v4.19+ Reported-by: Giuseppe Scrivano <gscrivan@redhat.com> Signed-off-by: Vivek Goyal <vgoyal@redhat.com> Signed-off-by: Miklos Szeredi <mszeredi@redhat.com>
-rw-r--r--fs/overlayfs/copy_up.c31
1 files changed, 18 insertions, 13 deletions
diff --git a/fs/overlayfs/copy_up.c b/fs/overlayfs/copy_up.c
index 9e62dcf06fc4..48119b23375b 100644
--- a/fs/overlayfs/copy_up.c
+++ b/fs/overlayfs/copy_up.c
@@ -443,6 +443,24 @@ static int ovl_copy_up_inode(struct ovl_copy_up_ctx *c, struct dentry *temp)
443{ 443{
444 int err; 444 int err;
445 445
446 /*
447 * Copy up data first and then xattrs. Writing data after
448 * xattrs will remove security.capability xattr automatically.
449 */
450 if (S_ISREG(c->stat.mode) && !c->metacopy) {
451 struct path upperpath, datapath;
452
453 ovl_path_upper(c->dentry, &upperpath);
454 if (WARN_ON(upperpath.dentry != NULL))
455 return -EIO;
456 upperpath.dentry = temp;
457
458 ovl_path_lowerdata(c->dentry, &datapath);
459 err = ovl_copy_up_data(&datapath, &upperpath, c->stat.size);
460 if (err)
461 return err;
462 }
463
446 err = ovl_copy_xattr(c->lowerpath.dentry, temp); 464 err = ovl_copy_xattr(c->lowerpath.dentry, temp);
447 if (err) 465 if (err)
448 return err; 466 return err;
@@ -460,19 +478,6 @@ static int ovl_copy_up_inode(struct ovl_copy_up_ctx *c, struct dentry *temp)
460 return err; 478 return err;
461 } 479 }
462 480
463 if (S_ISREG(c->stat.mode) && !c->metacopy) {
464 struct path upperpath, datapath;
465
466 ovl_path_upper(c->dentry, &upperpath);
467 BUG_ON(upperpath.dentry != NULL);
468 upperpath.dentry = temp;
469
470 ovl_path_lowerdata(c->dentry, &datapath);
471 err = ovl_copy_up_data(&datapath, &upperpath, c->stat.size);
472 if (err)
473 return err;
474 }
475
476 if (c->metacopy) { 481 if (c->metacopy) {
477 err = ovl_check_setxattr(c->dentry, temp, OVL_XATTR_METACOPY, 482 err = ovl_check_setxattr(c->dentry, temp, OVL_XATTR_METACOPY,
478 NULL, 0, -EOPNOTSUPP); 483 NULL, 0, -EOPNOTSUPP);