From: Vivek Goyal <vgoyal@redhat.com>
To: qemu-devel@nongnu.org, virtio-fs@redhat.com
Cc: lhenriques@suse.de, dgilbert@redhat.com, stefanha@redhat.com,
miklos@szeredi.hu
Subject: Re: [PATCH v3 0/2] virtiofsd: Enable posix_acl by default
Date: Wed, 24 Feb 2021 09:58:51 -0500 [thread overview]
Message-ID: <20210224145851.GC3148@redhat.com> (raw)
In-Reply-To: <20210223225250.23945-1-vgoyal@redhat.com>
On Tue, Feb 23, 2021 at 05:52:48PM -0500, Vivek Goyal wrote:
> Hi,
>
> This is V3 of the patches. Changes since v2 are.
>
> - I dropped the patch to give user an option to enable/disable acls.
> Now acls are enabled by default if xattrs are enabled and fuse
> client offers FUSE_POSIX_ACL capability.
>
> Miklos mentioned that ACLS might not have lot of overhead as these
> can be cached. So it might make sense to enable these by default.
Maybe ACL caching will only work well with cache=auto and cache=always.
With cache=none it probably will show most extra overhead.
For example, with cache=none, I did "su test". And then did "cat foo.txt"
and every time it results in two GETXATTR(system.posix_acl_access) calls.
2021-02-24 09:56:09.45-0500] [ID: 00000004] lo_getxattr(ino=1, name=system.posix_acl_access size=4096)
[2021-02-24 09:56:09.45-0500] [ID: 00000004] lo_getxattr(ino=2, name=system.posix_acl_access size=4096)
So this will definitely impact the performance with cache=none negatively.
I am now inclined to respin the patches and add options to enable/disable
acl and keep acl disabled by default. Those who need it, can enable it.
Vivek
>
> If we run into performance issues, then we can add another patch to
> give option to enable/disable and disable it by default.
>
> Luis Henriques reported that fstest generic/099 fails with virtiofs.
> Little debugging showed that we don't enable acl support. This
> patch series should fix the issue
>
> Vivek Goyal (2):
> virtiofsd: Add umask to seccom allow list
> virtiofsd: Enable posix_acls by default if xattrs are enabled
>
> tools/virtiofsd/passthrough_ll.c | 29 +++++++++++++++++++++------
> tools/virtiofsd/passthrough_seccomp.c | 1 +
> 2 files changed, 24 insertions(+), 6 deletions(-)
>
> --
> 2.25.4
>
prev parent reply other threads:[~2021-02-24 15:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-23 22:52 [PATCH v3 0/2] virtiofsd: Enable posix_acl by default Vivek Goyal
2021-02-23 22:52 ` [PATCH v3 1/2] virtiofsd: Add umask to seccom allow list Vivek Goyal
2021-02-24 12:25 ` Stefan Hajnoczi
2021-02-23 22:52 ` [PATCH v3 2/2] virtiofsd: Enable posix_acls by default if xattrs are enabled Vivek Goyal
2021-02-24 15:02 ` Stefan Hajnoczi
2021-02-24 14:58 ` Vivek Goyal [this message]
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=20210224145851.GC3148@redhat.com \
--to=vgoyal@redhat.com \
--cc=dgilbert@redhat.com \
--cc=lhenriques@suse.de \
--cc=miklos@szeredi.hu \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@redhat.com \
--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).