virtiofsd: Add support to enable/disable posix acls
v5 cover virtiofsd: Add support to enable/disable posix acls
Hi,
This is V5 of the patches.
Changes since V4:
- Added support to clear SGID while setting posix access acl. fuse client sends this information in a flag in SETXATTR message. This also requires opting in for using SETXATTR V2.
These patches have dependency on fuse kernel patches. So kernel patches need to be get merged first.
https://lore.kernel.org/linux-fsdevel/[email protected]/
Posting patches anyway, so that patches can get reviewed and tested.
Thanks
Vivek
Vivek Goyal (5):
virtiofsd: Add umask to seccom allow list
virtiofsd: Add capability to change/restore umask
virtiofsd: Add an option to enable/disable posix acls
virtiofsd: Add support for setxattr_v2
virtiofsd: Switch creds, drop FSETID for system.posix_acl_access xattr
docs/tools/virtiofsd.rst | 3 + include/standard-headers/linux/fuse.h | 19 ++- tools/virtiofsd/fuse_common.h | 6 + tools/virtiofsd/fuse_lowlevel.c | 42 ++++++- tools/virtiofsd/fuse_lowlevel.h | 3 +- tools/virtiofsd/helper.c | 1 + tools/virtiofsd/passthrough_ll.c | 166 ++++++++++++++++++++++++-- tools/virtiofsd/passthrough_seccomp.c | 1 + 8 files changed, 230 insertions(+), 11 deletions(-)
Signature · 1 line
2.25.4
PATCH v5 1/5 virtiofsd: Add umask to seccom allow list
Patches in this series are going to make use of "umask" syscall. So allow it.
--- tools/virtiofsd/passthrough_seccomp.c | 1 + 1 file changed, 1 insertion(+)
tools/virtiofsd/passthrough_seccomp.c +1 -0
@@ -114,6 +114,7 @@ static const int syscall_allowlist[] = {SCMP_SYS (utimensat),SCMP_SYS (write),SCMP_SYS (writev), + SCMP_SYS(umask), };/* Syscalls used when --syslog is enabled */
Signature · 1 line
2.25.4
PATCH v5 2/5 virtiofsd: Add capability to change/restore umask
In reply to Vivek GoyalWhen parent directory has default acl and a file is created in that directory, then umask is ignored and final file permissions are determined using default acl instead. (man 2 umask).
Currently, fuse applies the umask and sends modified mode in create request accordingly. fuse server can set FUSE_DONT_MASK and tell fuse client to not apply umask and fuse server will take care of it as needed.
With posix acls enabled, requirement will be that we want umask to determine final file mode if parent directory does not have default acl.
So if posix acls are enabled, opt in for FUSE_DONT_MASK. virtiofsd will set umask of the thread doing file creation. And host kernel should use that umask if parent directory does not have default acls, otherwise umask does not take affect.
Miklos mentioned that we already call unshare(CLONE_FS) for every thread. That means umask has now become property of per thread and it should be ok to manipulate it in file creation path.
This patch only adds capability to change umask and restore it. It does not enable it yet. Next patch will add capability to enable it based on if user enabled posix_acl or not.
This should fix fstest generic/099.
--- tools/virtiofsd/passthrough_ll.c | 22 ++++++++++++++++------ 1 file changed, 16 insertions(+), 6 deletions(-)
tools/virtiofsd/passthrough_ll.c +16 -6
@@ -122,6 +122,7 @@ struct lo_inode {struct lo_cred {uid_t euid;gid_t egid; +mode_t umask; };enum {
@@ -172,6 +173,8 @@ struct lo_data {/* An O_PATH file descriptor to /proc/self/fd/ */ int proc_self_fd;int user_killpriv_v2, killpriv_v2; +/* If set, virtiofsd is responsible for setting umask during creation */ +bool change_umask; };static const struct fuse_opt lo_opts[] = {
@@ -1134,7 +1137,8 @@ static void lo_lookup(fuse_req_t req, fuse_ino_t parent, const char *name)* ownership of caller. * TODO: What about selinux context? */ -static int lo_change_cred (fuse_req_t req,struct lo_cred *old) +static int lo_change_cred (fuse_req_t req,struct lo_cred *old, +bool change_umask) {int res;
@@ -1154,11 +1158,14 @@ static int lo_change_cred(fuse_req_t req, struct lo_cred *old)return errno_save; } +if (change_umask) { + old->umask =umask (req->ctx.umask); + }return 0 ; }/* Regain Privileges */ -static void lo_restore_cred (struct lo_cred *old) +static void lo_restore_cred (struct lo_cred *old,bool restore_umask) {int res;
@@ -1173,6 +1180,9 @@ static void lo_restore_cred(struct lo_cred *old)fuse_log (FUSE_LOG_ERR ,"setegid(%u): %m\n" , old->egid);exit (1 ); } + +if (restore_umask) +umask (old->umask); } static void lo_mknod_symlink(fuse_req_t req, fuse_ino_t parent,
@@ -1202,7 +1212,7 @@ static void lo_mknod_symlink(fuse_req_t req, fuse_ino_t parent,return ; } - saverr =lo_change_cred (req, &old); + saverr =lo_change_cred (req, &old, lo->change_umask && !S_ISLNK (mode));if (saverr) { goto out; }
@@ -1211,7 +1221,7 @@ static void lo_mknod_symlink(fuse_req_t req, fuse_ino_t parent, saverr = errno; -lo_restore_cred (&old); +lo_restore_cred (&old, lo->change_umask && !S_ISLNK (mode));if (res ==-1 ) { goto out;
@@ -1918,7 +1928,7 @@ static void lo_create(fuse_req_t req, fuse_ino_t parent, const char *name,return ; } - err =lo_change_cred (req, &old); + err =lo_change_cred (req, &old, lo->change_umask);if (err) { goto out; }
@@ -1929,7 +1939,7 @@ static void lo_create(fuse_req_t req, fuse_ino_t parent, const char *name, fd =openat (parent_inode->fd, name, fi->flags |O_CREAT |O_EXCL , mode); err = fd ==-1 ? errno :0 ; -lo_restore_cred (&old); +lo_restore_cred (&old, lo->change_umask);/* Ignore the error if file exists and O_EXCL was not given */ if (err && (err !=EEXIST || (fi->flags &O_EXCL ))) {
Signature · 1 line
2.25.4
PATCH v5 3/5 virtiofsd: Add an option to enable/disable posix acls
In reply to Vivek Goyalfuse has an option FUSE_POSIX_ACL which needs to be opted in by fuse server to enable posix acls. As of now we are not opting in for this, so posix acls are disabled on virtiofs by default.
Add virtiofsd option "-o posix_acl/no_posix_acl" to let users enable/disable posix acl support. By default it is disabled as of now due to performance concerns with cache=none.
Currently even if file server has not opted in for FUSE_POSIX_ACL, user can still query acl and set acl, and system.posix_acl_access and system.posix_acl_default xattrs show up listxattr response.
Miklos said this is confusing. So he said lets block and filter system.posix_acl_access and system.posix_acl_default xattrs in getxattr/setxattr/listxattr if user has explicitly disabled posix acls using -o no_posix_acl.
As of now continuing to keeping the existing behavior if user did not specify any option to disable acl support due to concerns about backward compatibility.
--- docs/tools/virtiofsd.rst | 3 + tools/virtiofsd/helper.c | 1 + tools/virtiofsd/passthrough_ll.c | 103 ++++++++++++++++++++++++++++++- 3 files changed, 106 insertions(+), 1 deletion(-)
docs/tools/virtiofsd.rst +3 -0
@@ -101,6 +101,9 @@ Options Enable/disable extended attributes (xattr) on files and directories. The default is ``no_xattr``. + * posix_acl|no_posix_acl - + Enable/disable posix acl support. Posix ACLs are disabled by default`. + .. option:: --socket-path=PATH Listen on vhost-user UNIX domain socket at PATH.
tools/virtiofsd/helper.c +1 -0
@@ -183,6 +183,7 @@ void fuse_cmdline_help(void)" to virtiofsd from guest applications.\n" " default: no_allow_direct_io\n" " -o announce_submounts Announce sub-mount points to the guest\n" +" -o posix_acl/no_posix_acl Enable/Disable posix_acl. (default: disabled)\n" ); }
tools/virtiofsd/passthrough_ll.c +102 -1
169 lines not on this page · raw message
Signature · 1 line
2.25.4
PATCH v5 4/5 virtiofsd: Add support for setxattr_v2
In reply to Vivek GoyalAdd the bits to enable support for setxattr_v2 if fuse offers it.
--- include/standard-headers/linux/fuse.h | 12 +++++++- tools/virtiofsd/fuse_common.h | 6 ++++ tools/virtiofsd/fuse_lowlevel.c | 42 ++++++++++++++++++++++++++- tools/virtiofsd/fuse_lowlevel.h | 3 +- tools/virtiofsd/passthrough_ll.c | 3 +- 5 files changed, 62 insertions(+), 4 deletions(-)
include/standard-headers/linux/fuse.h +11 -1
@@ -179,6 +179,7 @@* 7.33 * - add FUSE_HANDLE_KILLPRIV_V2, FUSE_WRITE_KILL_SUIDGID, FATTR_KILL_SUIDGID * - add FUSE_OPEN_KILL_SUIDGID +* - add FUSE_SETXATTR_V2 */ #ifndef _LINUX_FUSE_H
@@ -210,7 +211,7 @@#define FUSE_KERNEL_VERSION 7/** Minor version number of this interface */ -#define FUSE_KERNEL_MINOR_VERSION 33 +#define FUSE_KERNEL_MINOR_VERSION 34/** The node ID of the root inode */ #define FUSE_ROOT_ID 1
@@ -326,6 +327,7 @@ struct fuse_file_lock {* does not have CAP_FSETID. Additionally upon * write/truncate sgid is killed only if file has group * execute permission. (Same as Linux VFS behavior). +* FUSE_SETXATTR_V2: Does file server support V2 of struct fuse_setxattr_in */ #define FUSE_ASYNC_READ (1 << 0)#define FUSE_POSIX_LOCKS (1 << 1)
@@ -356,6 +358,7 @@ struct fuse_file_lock {#define FUSE_MAP_ALIGNMENT (1 << 26)#define FUSE_SUBMOUNTS (1 << 27)#define FUSE_HANDLE_KILLPRIV_V2 (1 << 28) +#define FUSE_SETXATTR_V2 (1 << 29)/** * CUSE INIT request/reply flags
@@ -682,6 +685,13 @@ struct fuse_setxattr_in {uint32_t flags; }; +struct fuse_setxattr_in_v2 { +uint32_t size; +uint32_t flags; +uint32_t setxattr_flags; +uint32_t padding; +}; +struct fuse_getxattr_in {uint32_t size;uint32_t padding;
tools/virtiofsd/fuse_common.h +6 -0
@@ -372,6 +372,12 @@ struct fuse_file_info {*/ #define FUSE_CAP_HANDLE_KILLPRIV_V2 (1 << 28) +/** +* Indicates that file server will expect "struct fuse_setxattr_in_v2" type +* of struct in setxattr requests +*/ +#define FUSE_CAP_SETXATTR_V2 (1 << 29) +/** * Ioctl flags *
tools/virtiofsd/fuse_lowlevel.c +41 -1
78 lines not on this page · raw message
tools/virtiofsd/fuse_lowlevel.h +2 -1
@@ -798,7 +798,8 @@ struct fuse_lowlevel_ops {* fuse_reply_err */ void (*setxattr)(fuse_req_t req,fuse_ino_t ino,const char *name, -const char *value,size_t size,int flags); +const char *value,size_t size,int flags, +uint32_t setxattr_flags);/** * Get an extended attribute
tools/virtiofsd/passthrough_ll.c +2 -1
@@ -3045,7 +3045,8 @@ out: }static void lo_setxattr (fuse_req_t req,fuse_ino_t ino,const char *in_name, -const char *value,size_t size,int flags) +const char *value,size_t size,int flags, +uint32_t extra_flags) {char procname[64 ];const char *name;
Signature · 1 line
2.25.4
PATCH v5 5/5 virtiofsd: Switch creds, drop FSETID for system.posix_acl_access xattr
In reply to Vivek GoyalWhen posix access acls are set on a file, it can lead to adjusting file permissions (mode) as well. If caller does not have CAP_FSETID and it also does not have membership of owner group, this will lead to clearing SGID bit in mode.
Current fuse code is written in such a way that it expects file server to take care of chaning file mode (permission), if there is a need. Right now, host kernel does not clear SGID bit because virtiofsd is running as root and has CAP_FSETID. For host kernel to clear SGID, virtiofsd need to switch to gid of caller in guest and also drop CAP_FSETID (if caller did not have it to begin with).
If SGID needs to be cleared, client will set the flag FUSE_SETXATTR_ACL_KILL_SGID in setxattr request. In that case server should kill sgid.
Currently just switch to uid/gid of the caller and drop CAP_FSETID and that should do it.
This should fix the xfstest generic/375 test case.
We don't have to switch uid for this to work. That could be one optimization that pass a parameter to lo_change_cred() to only switch gid and not uid.
Also this will not work whenever (if ever) we support idmapped mounts. In that case it is possible that uid/gid in request are 0/0 but still we need to clear SGID. So we will have to pick a non-root sgid and switch to that instead. That's an TODO item for future when idmapped mount support is introduced.
--- include/standard-headers/linux/fuse.h | 7 +++++ tools/virtiofsd/passthrough_ll.c | 42 +++++++++++++++++++++++++-- 2 files changed, 47 insertions(+), 2 deletions(-)
include/standard-headers/linux/fuse.h +7 -0
@@ -180,6 +180,7 @@* - add FUSE_HANDLE_KILLPRIV_V2, FUSE_WRITE_KILL_SUIDGID, FATTR_KILL_SUIDGID * - add FUSE_OPEN_KILL_SUIDGID * - add FUSE_SETXATTR_V2 +* - add FUSE_SETXATTR_ACL_KILL_SGID */ #ifndef _LINUX_FUSE_H
@@ -450,6 +451,12 @@ struct fuse_file_lock {*/ #define FUSE_OPEN_KILL_SUIDGID (1 << 0) +/** +* setxattr flags +* FUSE_SETXATTR_ACL_KILL_SGID: Clear SGID when system.posix_acl_access is set +*/ +#define FUSE_SETXATTR_ACL_KILL_SGID (1 << 0) +enum fuse_opcode {FUSE_LOOKUP =1 ,FUSE_FORGET =2 ,/* no reply */
tools/virtiofsd/passthrough_ll.c +40 -2
67 lines not on this page · raw message
Signature · 1 line
2.25.4
Re: [PATCH v5 5/5] virtiofsd: Switch creds, drop FSETID for system.posix_acl_access xattr
Quoted 76 lines · Vivek Goyal
When posix access acls are set on a file, it can lead to adjusting file permissions (mode) as well. If caller does not have
CAP_FSETIDand it also does not have membership of owner group, this will lead to clearing SGID bit in mode.Current fuse code is written in such a way that it expects file server to take care of chaning file mode (permission), if there is a need. Right now, host kernel does not clear SGID bit because virtiofsd is running as root and has
CAP_FSETID. For host kernel to clear SGID, virtiofsd need to switch to gid of caller in guest and also dropCAP_FSETID(if caller did not have it to begin with).If SGID needs to be cleared, client will set the flag
FUSE_SETXATTR_ACL_KILL_SGIDin setxattr request. In that case server should kill sgid.Currently just switch to uid/gid of the caller and drop
CAP_FSETIDand that should do it.This should fix the xfstest generic/375 test case.
We don't have to switch uid for this to work. That could be one optimization that pass a parameter to
lo_change_cred()to only switch gid and not uid.Also this will not work whenever (if ever) we support idmapped mounts. In that case it is possible that uid/gid in request are 0/0 but still we need to clear SGID. So we will have to pick a non-root sgid and switch to that instead. That's an TODO item for future when idmapped mount support is introduced.
Reported-by Luis Henriques <[email protected]>Signed-off-by Vivek Goyal <[email protected]>--- include/standard-headers/linux/fuse.h | 7 +++++ tools/virtiofsd/passthrough_ll.c | 42 +++++++++++++++++++++++++-- 2 files changed, 47 insertions(+), 2 deletions(-)include/standard-headers/linux/fuse.h +7
-0@@ -180,6 +180,7 @@* - add FUSE_HANDLE_KILLPRIV_V2, FUSE_WRITE_KILL_SUIDGID, FATTR_KILL_SUIDGID * - add FUSE_OPEN_KILL_SUIDGID * - add FUSE_SETXATTR_V2 +* - add FUSE_SETXATTR_ACL_KILL_SGID */ #ifndef _LINUX_FUSE_H@@ -450,6 +451,12 @@ struct fuse_file_lock {*/ #define FUSE_OPEN_KILL_SUIDGID (1 << 0) +/** +* setxattr flags +* FUSE_SETXATTR_ACL_KILL_SGID: Clear SGID when system.posix_acl_access is set +*/ +#define FUSE_SETXATTR_ACL_KILL_SGID (1 << 0) +enum fuse_opcode {FUSE_LOOKUP =1 ,FUSE_FORGET =2 ,/* no reply */ tools/virtiofsd/passthrough_ll.c +1
-1@@ -175,7 +175,7 @@ struct lo_data {int user_killpriv_v2, killpriv_v2;/* If set, virtiofsd is responsible for setting umask during creation */ bool change_umask; -int user_posix_acl; +int user_posix_acl, posix_acl; };static const struct fuse_opt lo_opts[] = {
tools/virtiofsd/passthrough_ll.c static void lo_init(void *userdata, struct fuse_conn_info *conn) · line 720
Quoted 6 lines
tools/virtiofsd/passthrough_ll.c +2
-1@@ -716,8 +716,10 @@ static void lo_init(void *userdata, struct fuse_conn_info *conn)* in fuse_lowlevel.c */ fuse_log (FUSE_LOG_DEBUG ,"lo_init: enabling posix acl\n" ); - conn->want |=FUSE_CAP_POSIX_ACL |FUSE_CAP_DONT_MASK ; + conn->want |=FUSE_CAP_POSIX_ACL |FUSE_CAP_DONT_MASK | +FUSE_CAP_SETXATTR_V2 ;
An annoying thing with this is that if we're using a kernel without _V2 support the mount will still succeed. But we'll see:
ls: cannot access '/mnt': Connection refused
and in the userspace:
fuse: error: filesystem requested capabilities 0x20000000 that are not supported by kernel, aborting.
Maybe it would be worth to automatically disable acl support if this happens (with an error message) but still allow the filesystem to be used. Or, which is probably better, to handle the EPROTO error in the kernel during mount.
Cheers,
--
Luís
Quoted 57 lines
tools/virtiofsd/passthrough_ll.c +37
-0lo->change_umask = true; + lo->posix_acl = true; }else {/* User either did not specify anything or wants it disabled */ fuse_log (FUSE_LOG_DEBUG ,"lo_init: disabling posix_acl\n" );@@ -3092,12 +3094,48 @@ static void lo_setxattr(fuse_req_t req, fuse_ino_t ino, const char *in_name,sprintf (procname,"%i" , inode->fd);if (S_ISREG (inode->filetype) ||S_ISDIR (inode->filetype)) { +bool switched_creds = false; +struct lo_cred old = {}; + fd =openat (lo->proc_self_fd, procname,O_RDONLY );if (fd <0 ) { saverr = errno; goto out; } + +/* +* If we are setting posix access acl and if SGID needs to be +* cleared, then switch to caller's gid and drop CAP_FSETID +* and that should make sure host kernel clears SGID. +* +* This probably will not work when we support idmapped mounts. +* In that case we will need to find a non-root gid and switch +* to it. (Instead of gid in request). Fix it when we support +* idmapped mounts. +*/ +if (lo->posix_acl && !strcmp (name,"system.posix_acl_access" ) + && (extra_flags &FUSE_SETXATTR_ACL_KILL_SGID )) { + ret =lo_change_cred (req, &old, false); +if (ret) { + saverr = ret; + goto out; + } + ret =drop_effective_cap ("FSETID" ,NULL ); +if (ret !=0 ) { +lo_restore_cred (&old, false); + saverr = ret; + goto out; + } + switched_creds = true; + } + ret =fsetxattr (fd, name, value, size, flags); + +if (switched_creds) { +if (gain_effective_cap ("FSETID" )) +fuse_log (FUSE_LOG_ERR ,"Failed to gain CAP_FSETID\n" ); +lo_restore_cred (&old, false); + } }else {/* fchdir should not fail here */ assert (fchdir (lo->proc_self_fd) ==0 );Signature · 1 line
2.25.4
Re: [PATCH v5 5/5] virtiofsd: Switch creds, drop FSETID for system.posix_acl_access xattr
Quoted 89 lines · Luis Henriques
Quoted 76 lines · Vivek Goyal
When posix access acls are set on a file, it can lead to adjusting file permissions (mode) as well. If caller does not have
CAP_FSETIDand it also does not have membership of owner group, this will lead to clearing SGID bit in mode.Current fuse code is written in such a way that it expects file server to take care of chaning file mode (permission), if there is a need. Right now, host kernel does not clear SGID bit because virtiofsd is running as root and has
CAP_FSETID. For host kernel to clear SGID, virtiofsd need to switch to gid of caller in guest and also dropCAP_FSETID(if caller did not have it to begin with).If SGID needs to be cleared, client will set the flag
FUSE_SETXATTR_ACL_KILL_SGIDin setxattr request. In that case server should kill sgid.Currently just switch to uid/gid of the caller and drop
CAP_FSETIDand that should do it.This should fix the xfstest generic/375 test case.
We don't have to switch uid for this to work. That could be one optimization that pass a parameter to
lo_change_cred()to only switch gid and not uid.Also this will not work whenever (if ever) we support idmapped mounts. In that case it is possible that uid/gid in request are 0/0 but still we need to clear SGID. So we will have to pick a non-root sgid and switch to that instead. That's an TODO item for future when idmapped mount support is introduced.
Reported-by Luis Henriques <[email protected]>Signed-off-by Vivek Goyal <[email protected]>--- include/standard-headers/linux/fuse.h | 7 +++++ tools/virtiofsd/passthrough_ll.c | 42 +++++++++++++++++++++++++-- 2 files changed, 47 insertions(+), 2 deletions(-)include/standard-headers/linux/fuse.h +7
-0@@ -180,6 +180,7 @@* - add FUSE_HANDLE_KILLPRIV_V2, FUSE_WRITE_KILL_SUIDGID, FATTR_KILL_SUIDGID * - add FUSE_OPEN_KILL_SUIDGID * - add FUSE_SETXATTR_V2 +* - add FUSE_SETXATTR_ACL_KILL_SGID */ #ifndef _LINUX_FUSE_H@@ -450,6 +451,12 @@ struct fuse_file_lock {*/ #define FUSE_OPEN_KILL_SUIDGID (1 << 0) +/** +* setxattr flags +* FUSE_SETXATTR_ACL_KILL_SGID: Clear SGID when system.posix_acl_access is set +*/ +#define FUSE_SETXATTR_ACL_KILL_SGID (1 << 0) +enum fuse_opcode {FUSE_LOOKUP =1 ,FUSE_FORGET =2 ,/* no reply */ tools/virtiofsd/passthrough_ll.c +1
-1@@ -175,7 +175,7 @@ struct lo_data {int user_killpriv_v2, killpriv_v2;/* If set, virtiofsd is responsible for setting umask during creation */ bool change_umask; -int user_posix_acl; +int user_posix_acl, posix_acl; };static const struct fuse_opt lo_opts[] = {tools/virtiofsd/passthrough_ll.c static void lo_init(void *userdata, struct fuse_conn_info *conn) · line 720
Quoted 6 lines
tools/virtiofsd/passthrough_ll.c +2
-1@@ -716,8 +716,10 @@ static void lo_init(void *userdata, struct fuse_conn_info *conn)* in fuse_lowlevel.c */ fuse_log (FUSE_LOG_DEBUG ,"lo_init: enabling posix acl\n" ); - conn->want |=FUSE_CAP_POSIX_ACL |FUSE_CAP_DONT_MASK ; + conn->want |=FUSE_CAP_POSIX_ACL |FUSE_CAP_DONT_MASK | +FUSE_CAP_SETXATTR_V2 ;An annoying thing with this is that if we're using a kernel without
_V2support the mount will still succeed. But we'll see:ls: cannot access '/mnt': Connection refused
Quoted 7 lines
and in the userspace:
fuse: error: filesystem requested capabilities
0x20000000that are not supported by kernel, aborting.Maybe it would be worth to automatically disable acl support if this happens (with an error message) but still allow the filesystem to be used.
If user specific "-o posix_acl" then it is better to fail explicitly if posix_acl can't be enabled. If user did not specify anything, then it makes sense to automatically disable posix acl and continue.
Quoted 2 lines
Or, which is probably better, to handle the EPROTO error in the kernel during mount.
This will have been idea but in fuse, init process handling happens asynchronously. That is mount returns to user space while init command might complete at a later point of time. So can't return -EPROTO at mount time.
So one of the problems seem to be that error message is not very clear. How about adding following so that user is clear that posix acl can't be enabled.
Vivek
--- tools/virtiofsd/passthrough_ll.c | 14 +++++++++++--- 1 file changed, 11 insertions(+), 3 deletions(-)
tools/virtiofsd/passthrough_ll.c +11 -3
@@ -712,10 +712,18 @@ static void lo_init(void *userdata, struif (lo->user_posix_acl ==1 ) {/* * User explicitly asked for this option. Enable it unconditionally. -* If connection does not have this capability, it should fail -* in fuse_lowlevel.c +* If connection does not have this capability, give out message +* now. fuse_lowlevel.c will error out. */ -fuse_log (FUSE_LOG_DEBUG ,"lo_init: enabling posix acl\n" ); +if (!(conn->capable &FUSE_CAP_POSIX_ACL ) || + !(conn->capable &FUSE_CAP_DONT_MASK ) || + !(conn->capable &FUSE_CAP_SETXATTR_V2 )) { +fuse_log (FUSE_LOG_ERR ,"lo_init: Can not enable posix acl." +" kernel does not support FUSE_POSIX_ACL, FUSE_DONT_MASK" +" or FUSE_SETXATTR_V2 capability.\n" ); + }else { +fuse_log (FUSE_LOG_DEBUG ,"lo_init: enabling posix acl\n" ); + } conn->want |=FUSE_CAP_POSIX_ACL |FUSE_CAP_DONT_MASK |FUSE_CAP_SETXATTR_V2 ; lo->change_umask = true;
Re: [PATCH v5 5/5] virtiofsd: Switch creds, drop FSETID for system.posix_acl_access xattr
Quoted 102 lines · Vivek Goyal
Quoted 89 lines · Luis Henriques
Quoted 76 lines · Vivek Goyal
When posix access acls are set on a file, it can lead to adjusting file permissions (mode) as well. If caller does not have
CAP_FSETIDand it also does not have membership of owner group, this will lead to clearing SGID bit in mode.Current fuse code is written in such a way that it expects file server to take care of chaning file mode (permission), if there is a need. Right now, host kernel does not clear SGID bit because virtiofsd is running as root and has
CAP_FSETID. For host kernel to clear SGID, virtiofsd need to switch to gid of caller in guest and also dropCAP_FSETID(if caller did not have it to begin with).If SGID needs to be cleared, client will set the flag
FUSE_SETXATTR_ACL_KILL_SGIDin setxattr request. In that case server should kill sgid.Currently just switch to uid/gid of the caller and drop
CAP_FSETIDand that should do it.This should fix the xfstest generic/375 test case.
We don't have to switch uid for this to work. That could be one optimization that pass a parameter to
lo_change_cred()to only switch gid and not uid.Also this will not work whenever (if ever) we support idmapped mounts. In that case it is possible that uid/gid in request are 0/0 but still we need to clear SGID. So we will have to pick a non-root sgid and switch to that instead. That's an TODO item for future when idmapped mount support is introduced.
Reported-by Luis Henriques <[email protected]>Signed-off-by Vivek Goyal <[email protected]>--- include/standard-headers/linux/fuse.h | 7 +++++ tools/virtiofsd/passthrough_ll.c | 42 +++++++++++++++++++++++++-- 2 files changed, 47 insertions(+), 2 deletions(-)include/standard-headers/linux/fuse.h +7
-0@@ -180,6 +180,7 @@* - add FUSE_HANDLE_KILLPRIV_V2, FUSE_WRITE_KILL_SUIDGID, FATTR_KILL_SUIDGID * - add FUSE_OPEN_KILL_SUIDGID * - add FUSE_SETXATTR_V2 +* - add FUSE_SETXATTR_ACL_KILL_SGID */ #ifndef _LINUX_FUSE_H@@ -450,6 +451,12 @@ struct fuse_file_lock {*/ #define FUSE_OPEN_KILL_SUIDGID (1 << 0) +/** +* setxattr flags +* FUSE_SETXATTR_ACL_KILL_SGID: Clear SGID when system.posix_acl_access is set +*/ +#define FUSE_SETXATTR_ACL_KILL_SGID (1 << 0) +enum fuse_opcode {FUSE_LOOKUP =1 ,FUSE_FORGET =2 ,/* no reply */ tools/virtiofsd/passthrough_ll.c +1
-1@@ -175,7 +175,7 @@ struct lo_data {int user_killpriv_v2, killpriv_v2;/* If set, virtiofsd is responsible for setting umask during creation */ bool change_umask; -int user_posix_acl; +int user_posix_acl, posix_acl; };static const struct fuse_opt lo_opts[] = {tools/virtiofsd/passthrough_ll.c static void lo_init(void *userdata, struct fuse_conn_info *conn) · line 720
Quoted 6 lines
tools/virtiofsd/passthrough_ll.c +2
-1@@ -716,8 +716,10 @@ static void lo_init(void *userdata, struct fuse_conn_info *conn)* in fuse_lowlevel.c */ fuse_log (FUSE_LOG_DEBUG ,"lo_init: enabling posix acl\n" ); - conn->want |=FUSE_CAP_POSIX_ACL |FUSE_CAP_DONT_MASK ; + conn->want |=FUSE_CAP_POSIX_ACL |FUSE_CAP_DONT_MASK | +FUSE_CAP_SETXATTR_V2 ;An annoying thing with this is that if we're using a kernel without
_V2support the mount will still succeed. But we'll see:ls: cannot access '/mnt': Connection refused
Quoted 7 lines
and in the userspace:
fuse: error: filesystem requested capabilities
0x20000000that are not supported by kernel, aborting.Maybe it would be worth to automatically disable acl support if this happens (with an error message) but still allow the filesystem to be used.
If user specific "-o
posix_acl" then it is better to fail explicitly ifposix_aclcan't be enabled. If user did not specify anything, then it makes sense to automatically disable posix acl and continue.
Quoted 7 lines
Quoted 2 lines
Or, which is probably better, to handle the EPROTO error in the kernel during mount.
This will have been idea but in fuse, init process handling happens asynchronously. That is mount returns to user space while init command might complete at a later point of time. So can't return
-EPROTOat mount time.
Oh, right. I remember the first time I looked that I found it a bit odd that fuse_send_init() didn't wait to return an error. So, my suggestion isn't feasible.
Quoted 3 lines
So one of the problems seem to be that error message is not very clear. How about adding following so that user is clear that posix acl can't be enabled.
Thanks, I think this extra information is indeed useful.
Cheers,
--
Luís
Quoted 35 lines
Vivek
--- tools/virtiofsd/passthrough_ll.c | 14 +++++++++++--- 1 file changed, 11 insertions(+), 3 deletions(-)Index:
rhvgoyal-qemu/tools/virtiofsd/passthrough_ll.c
===================================================================tools/virtiofsd/passthrough_ll.c +11
-3@@ -712,10 +712,18 @@ static void lo_init(void *userdata, struif (lo->user_posix_acl ==1 ) {/* * User explicitly asked for this option. Enable it unconditionally. -* If connection does not have this capability, it should fail -* in fuse_lowlevel.c +* If connection does not have this capability, give out message +* now. fuse_lowlevel.c will error out. */ -fuse_log (FUSE_LOG_DEBUG ,"lo_init: enabling posix acl\n" ); +if (!(conn->capable &FUSE_CAP_POSIX_ACL ) || + !(conn->capable &FUSE_CAP_DONT_MASK ) || + !(conn->capable &FUSE_CAP_SETXATTR_V2 )) { +fuse_log (FUSE_LOG_ERR ,"lo_init: Can not enable posix acl." +" kernel does not support FUSE_POSIX_ACL, FUSE_DONT_MASK" +" or FUSE_SETXATTR_V2 capability.\n" ); + }else { +fuse_log (FUSE_LOG_DEBUG ,"lo_init: enabling posix acl\n" ); + } conn->want |=FUSE_CAP_POSIX_ACL |FUSE_CAP_DONT_MASK |FUSE_CAP_SETXATTR_V2 ; lo->change_umask = true;
Patchew URL: https://patchew.org/QEMU/[email protected]/
Patchew URL: https://patchew.org/QEMU/[email protected]/
Hi,
This series seems to have some coding style problems. See output below for more information:
Type: series
Message-id: [email protected]
Subject: [PATCH v5 0/5] virtiofsd: Add support to enable/disable posix acls
=== TEST SCRIPT BEGIN ===
#!/bin/bash
git rev-parse base > /dev/null || exit 0
git config --local diff.renamelimit 0
git config --local diff.renames True
git config --local diff.algorithm histogram./scripts/checkpatch.pl --mailback base..
=== TEST SCRIPT END ===
Updating 3c8cf5a9c21ff8782164d1def7f44bd888713384
Quoted 1 line
* [new tag] patchew/[email protected] -> patchew/[email protected]
Switched to a new branch 'test'
ea606d9 virtiofsd: Switch creds, drop FSETID for system.posix_acl_access xattr bc9a877 virtiofsd: Add support for setxattr_v2
d28413e virtiofsd: Add an option to enable/disable posix acls 1eeb11f virtiofsd: Add capability to change/restore umask
0b02a25 virtiofsd: Add umask to seccom allow list
=== OUTPUT BEGIN ===
1/5 Checking commit 0b02a2507048 (virtiofsd: Add umask to seccom allow list) 2/5 Checking commit 1eeb11f00fdb (virtiofsd: Add capability to change/restore umask) 3/5 Checking commit d28413e66e58 (virtiofsd: Add an option to enable/disable posix acls)
WARNING: line over 80 characters
#239: FILE: tools/virtiofsd/passthrough_ll.c:3957:
+ fuse_log(FUSE_LOG_ERR, "Can't enable posix ACLs. xattrs are disabled.\n");
total: 0 errors, 1 warnings, 185 lines checked
Patch 3/5 has style problems, please review. If any of these errors
are false positives report them to the maintainer, see
CHECKPATCH in MAINTAINERS.
4/5 Checking commit bc9a8776c947 (virtiofsd: Add support for setxattr_v2)
5/5 Checking commit ea606d9de8f0 (virtiofsd: Switch creds, drop FSETID for system.posix_acl_access xattr)
ERROR: braces {} are necessary for all arms of this statement
#137: FILE: tools/virtiofsd/passthrough_ll.c:3135:
+ if (gain_effective_cap("FSETID"))
[...]
total: 1 errors, 0 warnings, 86 lines checked
Patch 5/5 has style problems, please review. If any of these errors are false positives report them to the maintainer, see CHECKPATCH in MAINTAINERS.
=== OUTPUT END ===
Test command exited with code: 1
The full log is available at
http://patchew.org/logs/[email protected]/testing.checkpatch/?type=message.
---
Email generated automatically by Patchew [https://patchew.org/].
Please send your feedback to [email protected]