Skip to contentSkip to conversation

overlayfs: check CAP_MKNOD before issuing vfs_whiteout

PATCH In review Mark Salyzyn 2 participants 4 messages Aug 28, 2018

Subsystems (2)
lore
Share & tools
lore
#0 lore raw

PATCH v5 2/3 overlayfs: check CAP_MKNOD before issuing vfs_whiteout

Assumption never checked, should fail if the mounter creds are not sufficient.

Cc Miklos Szeredi <[email protected]>
Cc Jonathan Corbet <[email protected]>
Cc Vivek Goyal <[email protected]>
Cc Eric W. Biederman <[email protected]>
Cc Amir Goldstein <[email protected]>
Cc Randy Dunlap <[email protected]>
Cc Stephen Smalley <[email protected]>

v5
- dependency of "overlayfs: override_creds=off option bypass creator_cred"

---
 fs/overlayfs/overlayfs.h | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
fs/overlayfs/overlayfs.h +1 -1
index 7538b9b56237..bf3a80157d42 100644
@@ -176,7 +176,7 @@ static inline int ovl_do_rename(struct inode *olddir, struct dentry *olddentry,
 
 static inline int ovl_do_whiteout(struct inode *dir, struct dentry *dentry)
 {
-	int err = vfs_whiteout(dir, dentry);
+	int err = capable(CAP_MKNOD) ? vfs_whiteout(dir, dentry) : -EPERM;
 	pr_debug("whiteout(%pd2) = %i\n", dentry, err);
 	return err;
 }
Signature · 1 line
2.19.0.rc0.228.g281dcd1b4d0-goog
maintainer
#1 lore raw
Quoted 27 lines · Mark Salyzyn

Assumption never checked, should fail if the mounter creds are not sufficient.

Cc Miklos Szeredi <[email protected]>
Cc Jonathan Corbet <[email protected]>
Cc Vivek Goyal <[email protected]>
Cc Eric W. Biederman <[email protected]>
Cc Amir Goldstein <[email protected]>
Cc Randy Dunlap <[email protected]>
Cc Stephen Smalley <[email protected]>

v5
- dependency of "overlayfs: override_creds=off option bypass creator_cred"

---
 fs/overlayfs/overlayfs.h | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
fs/overlayfs/overlayfs.h +0 -0
index 7538b9b56237..bf3a80157d42 100644

fs/overlayfs/overlayfs.h static inline int ovl_do_rename(struct inode *olddir, struct dentry *olddentry, · line 179

Quoted 5 lines
fs/overlayfs/overlayfs.h +1 -1
@@ -176,7 +176,7 @@ static inline int ovl_do_rename(struct inode *olddir, struct dentry *olddentry,
 
 static inline int ovl_do_whiteout(struct inode *dir, struct dentry *dentry)
 {
-       int err = vfs_whiteout(dir, dentry);
+       int err = capable(CAP_MKNOD) ? vfs_whiteout(dir, dentry) : -EPERM;

Should that be ns_capable()? Should the test go into vfs_whiteout()? I feel there is no convention at all.

Thanks,
Amir.

maintainer
#2 lore raw
Quoted 30 lines · Amir Goldstein
Quoted 28 lines · Mark Salyzyn

Assumption never checked, should fail if the mounter creds are not sufficient.

Cc Miklos Szeredi <[email protected]>
Cc Jonathan Corbet <[email protected]>
Cc Vivek Goyal <[email protected]>
Cc Eric W. Biederman <[email protected]>
Cc Amir Goldstein <[email protected]>
Cc Randy Dunlap <[email protected]>
Cc Stephen Smalley <[email protected]>

v5
- dependency of "overlayfs: override_creds=off option bypass creator_cred"

---
 fs/overlayfs/overlayfs.h | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
fs/overlayfs/overlayfs.h +0 -0
index 7538b9b56237..bf3a80157d42 100644
@@ -176,7 +176,7 @@ static inline int ovl_do_rename(struct inode *olddir, struct dentry *olddentry,
 
Quoted 8 lines

fs/overlayfs/overlayfs.h static inline int ovl_do_rename(struct inode *olddir, struct dentry *olddentry, · line 179

Quoted 4 lines
fs/overlayfs/overlayfs.h +1 -1
 static inline int ovl_do_whiteout(struct inode *dir, struct dentry *dentry)
 {
-       int err = vfs_whiteout(dir, dentry);
+       int err = capable(CAP_MKNOD) ? vfs_whiteout(dir, dentry) : -EPERM;

Should that be ns_capable()? Should the test go into vfs_whiteout()? I feel there is no convention at all.

Nevermind, I don't think creating a whiteout poses any risk, so don't think we need to worry about CAP_MKNOD.

Thanks,
Amir.

#3 lore raw
Quoted 36 lines · Amir Goldstein
Quoted 28 lines · Amir Goldstein
Quoted 27 lines · Mark Salyzyn

Assumption never checked, should fail if the mounter creds are not sufficient.

Cc Miklos Szeredi <[email protected]>
Cc Jonathan Corbet <[email protected]>
Cc Vivek Goyal <[email protected]>
Cc Eric W. Biederman <[email protected]>
Cc Amir Goldstein <[email protected]>
Cc Randy Dunlap <[email protected]>
Cc Stephen Smalley <[email protected]>

v5
- dependency of "overlayfs: override_creds=off option bypass creator_cred"

---
  fs/overlayfs/overlayfs.h | 2 +-
  1 file changed, 1 insertion(+), 1 deletion(-)
fs/overlayfs/overlayfs.h +0 -0
index 7538b9b56237..bf3a80157d42 100644
@@ -176,7 +176,7 @@ static inline int ovl_do_rename(struct inode *olddir, struct dentry *olddentry,
 
Quoted 7 lines

fs/overlayfs/overlayfs.h static inline int ovl_do_rename(struct inode *olddir, struct dentry *olddentry, · line 179

Quoted 4 lines
fs/overlayfs/overlayfs.h +1 -1
  static inline int ovl_do_whiteout(struct inode *dir, struct dentry *dentry)
  {
-       int err = vfs_whiteout(dir, dentry);
+       int err = capable(CAP_MKNOD) ? vfs_whiteout(dir, dentry) : -EPERM;

Should that be ns_capable()? Should the test go into vfs_whiteout()? I feel there is no convention at all.

Quoted 5 lines

Nevermind, I don't think creating a whiteout poses any risk, so don't think we need to worry about CAP_MKNOD.

Thanks,
Amir.

Ok, will discard from the set, we can address this later if it creates concern (as in, not a dependency to my proposed feature flag). So we feel that whiteout node in the writeable playground of workdir/upperdir is not in itself a security concern. Other (more dangerous) mknod will be checked against the caller's credentials coming in.

-- Mark