From: Vivek Goyal <vgoyal@redhat.com>
To: qemu-devel@nongnu.org, virtio-fs@redhat.com
Cc: lhenriques@suse.de, dgilbert@redhat.com, vgoyal@redhat.com,
miklos@szeredi.hu
Subject: [PATCH v6 0/5] virtiofsd: Add support to enable/disable posix acl
Date: Tue, 30 Mar 2021 10:09:20 -0400 [thread overview]
Message-ID: <20210330140925.730449-1-vgoyal@redhat.com> (raw)
Hi,
This is V6 of the patches.
Changes since V5:
- If user asked to enable posix acl and if it can't be enabled, give a
clear message before failure. (Luis).
- Took care of some coding style issues.
Corresponding kernel patches are posted here.
https://lore.kernel.org/linux-fsdevel/20210325151823.572089-1-vgoyal@redhat.com/
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 | 177 ++++++++++++++++++++++++--
tools/virtiofsd/passthrough_seccomp.c | 1 +
8 files changed, 241 insertions(+), 11 deletions(-)
--
2.25.4
next reply other threads:[~2021-03-30 14:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-30 14:09 Vivek Goyal [this message]
2021-03-30 14:09 ` [PATCH v6 1/5] virtiofsd: Add umask to seccom allow list Vivek Goyal
2021-03-30 14:09 ` [PATCH v6 2/5] virtiofsd: Add capability to change/restore umask Vivek Goyal
2021-03-30 14:09 ` [PATCH v6 3/5] virtiofsd: Add an option to enable/disable posix acls Vivek Goyal
2021-03-30 14:09 ` [PATCH v6 4/5] virtiofsd: Add support for setxattr_v2 Vivek Goyal
2021-03-30 14:09 ` [PATCH v6 5/5] virtiofsd: Switch creds, drop FSETID for system.posix_acl_access xattr Vivek Goyal
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210330140925.730449-1-vgoyal@redhat.com \
--to=vgoyal@redhat.com \
--cc=dgilbert@redhat.com \
--cc=lhenriques@suse.de \
--cc=miklos@szeredi.hu \
--cc=qemu-devel@nongnu.org \
--cc=virtio-fs@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).