From: "Jean-Pierre André" <jean-pierre.andre@wanadoo.fr>
To: Seth Forshee <seth.forshee@canonical.com>,
fuse-devel@lists.sourceforge.net, linux-fsdevel@vger.kernel.org
Cc: "Eric W. Biederman" <ebiederm@xmission.com>,
Miklos Szeredi <miklos@szeredi.hu>
Subject: Re: [fuse-devel] [RFC] fuse: Support posix ACLs
Date: Thu, 30 Jun 2016 09:13:33 +0200 [thread overview]
Message-ID: <5774C69D.7060507@wanadoo.fr> (raw)
In-Reply-To: <20160629190731.GF53123@ubuntu-hedt>
Seth Forshee wrote:
> Eric and I are working towards adding support for fuse mounts in
> non-init user namespaces. Towards that end we'd like to add ACL support
> to fuse as this will allow for a cleaner implementation overall. Below
My best wishes go with you.
> is an initial patch to support this. I'd like to get some general
> feedback on this patch and ask a couple of specific questions.
>
> There are some indications that fuse supports ACLs on the userspace side
> when default_permissions is not used (though I'm not seeing how that
> works). Will these changes conflict with that support, and if how do we
> avoid those conflicts?
ntfs-3g has both variants implemented. When supporting ACLs
within the userspace, it does not set default_permissions,
and it uses null cache timeouts.
When expecting ACLs supported at the kernel level, it sets
default_permissions and it uses non_null cache timeouts.
It sets FUSE_CAP_DONT_MASK in both cases.
I would expect default_permissions to make a clear divide
between those conditions, avoiding any conflicts.
Jean-Pierre
next prev parent reply other threads:[~2016-06-30 7:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-29 19:07 [RFC] fuse: Support posix ACLs Seth Forshee
2016-06-29 19:24 ` Michael j Theall
[not found] ` <OFF8F0F486.DB2CEB73-ON86257FE1.006A1FF4-86257FE1.006A9703-8eTO7WVQ4XIsd+ienQ86orlN3bxYEBpz@public.gmane.org>
2016-06-29 19:52 ` Michael j Theall
2016-06-29 21:03 ` [fuse-devel] " Seth Forshee
2016-06-29 21:13 ` Michael j Theall
2016-06-29 20:18 ` [fuse-devel] " Eric W. Biederman
[not found] ` <87vb0rhhpr.fsf-JOvCrm2gF+uungPnsOpG7nhyD016LWXt@public.gmane.org>
2016-06-29 20:35 ` Michael j Theall
2016-06-30 7:23 ` [fuse-devel] " Jean-Pierre André
2016-06-30 13:07 ` Seth Forshee
2016-06-30 16:25 ` Eric W. Biederman
2016-06-30 16:54 ` Seth Forshee
2016-07-01 19:37 ` Nikolaus Rath
2016-07-01 19:33 ` Nikolaus Rath
2016-07-01 19:49 ` Seth Forshee
2016-06-29 20:56 ` Seth Forshee
2016-06-30 7:13 ` Jean-Pierre André [this message]
2016-07-01 19:29 ` Nikolaus Rath
2016-07-01 19:58 ` Seth Forshee
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=5774C69D.7060507@wanadoo.fr \
--to=jean-pierre.andre@wanadoo.fr \
--cc=ebiederm@xmission.com \
--cc=fuse-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=seth.forshee@canonical.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.