linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Seth Forshee <seth.forshee@canonical.com>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: fuse-devel <fuse-devel@lists.sourceforge.net>,
	linux-fsdevel@vger.kernel.org,
	"Eric W. Biederman" <ebiederm@xmission.com>,
	"Michael j Theall" <mtheall@us.ibm.com>,
	"Jean-Pierre André" <jean-pierre.andre@wanadoo.fr>,
	"Nikolaus Rath" <Nikolaus@rath.org>,
	"Andreas Gruenbacher" <agruenba@redhat.com>
Subject: Re: [PATCH 0/2] Support for posix ACLs in fuse
Date: Wed, 21 Sep 2016 08:41:56 -0500	[thread overview]
Message-ID: <20160921134156.GA55138@ubuntu-hedt> (raw)
In-Reply-To: <CAJfpegvY=VZeEw8FoVqddQ_6vLiAF9dMR8PWOwAjg50K6rQ2yg@mail.gmail.com>

On Wed, Sep 21, 2016 at 10:30:14AM +0200, Miklos Szeredi wrote:
> [Adding Andreas Gruenbacher to Cc]
> 
> On Mon, Aug 29, 2016 at 3:46 PM, Seth Forshee
> <seth.forshee@canonical.com> wrote:
> > Hi Miklos,
> >
> > Here's an updated set of patches for supporting posix ACLs in fuse. I
> > think I've incorporated all the feedback from the last RFC series, and
> > so I've dropped the RFC this time.
> 
> Pushed, with minor changes, to
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/fuse.git#for-next
> 
> Please verify that I didn't break it.

I've reviewed the changes and they seem okay, still need to test.

> > I also pushed to github the changes I made to libfuse for testing this.
> > They're a little rough and probably not 100% complete, but it is
> > sufficient for exercising the functionality of these patches with
> > fusexmp.
> >
> >  https://github.com/sforshee/libfuse/tree/posix-acl
> 
> As for the libfuse part:
> 
> 1) Please don't mess with fusexmp.c.  The added code is really an
> anti-example.  Posix acls will will work fine in such pass-through
> filesystems without doing anything.  The added complexity just makes
> it brittle and racy without actually doing anything positive.

As you note below, it's hard to find a "real" filesystem to test it
with so fusexmp proved convenient for that. But I'll omit it when I
update the pull req.

> 2) You define some constants and structures (POSIX_ACL_*) in
> fuse_common.h that don't seem to belong there.  There's <sys/acl.h>
> that contains some parts of that, but I'm not sure how much we want to
> tie libfuse to libacl...  It's a difficult thing.  Generally I'd try
> to keep the interface as narrow as possible.  Perhaps it's enough to
> have a a function to return the equivalent mode from the xattr?

To be honest I only really meant that to serve as an example of all the
stuff that would need to happen in userspace based on the kernel
implementation. Looking now at libacl I guess it could just be expected
that filesystems will use that. It seems to provide the essentials to do
what I did with fusexmp at least, even an interface for getting the
equivalent mode (acl_equiv_mode). Not sure how well it works if e.g. a
filesystem needs to convert between the posix ACL format and some
different format native to that filesystem.

> 3) How will richacl's fit into this?

I don't know, I haven't looked at those patches closely, but in git I'm
not seeing any support for richacls in fuse yet anyhow.

Thanks,
Seth

  parent reply	other threads:[~2016-09-21 13:41 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-29 13:46 [PATCH 0/2] Support for posix ACLs in fuse Seth Forshee
2016-08-29 13:46 ` [PATCH 1/2] fuse: Use generic xattr ops Seth Forshee
2016-08-29 13:46 ` [PATCH 2/2] fuse: Add posix ACL support Seth Forshee
2016-09-07  3:32 ` [PATCH 0/2] Support for posix ACLs in fuse Nikolaus Rath
2016-09-07 12:32   ` Seth Forshee
2016-09-21  8:30 ` Miklos Szeredi
2016-09-21 12:25   ` Jean-Pierre André
2016-09-21 14:14     ` Miklos Szeredi
2016-09-21 20:50       ` [fuse-devel] " Michael Theall
2016-09-23 15:03         ` Miklos Szeredi
2016-09-21 13:41   ` Seth Forshee [this message]
2016-09-21 13:57     ` Miklos Szeredi
2016-09-28 19:34     ` Seth Forshee
2016-09-21 15:40   ` Eric W. Biederman
2016-09-21 17:24     ` Andreas Grünbacher
2016-09-21 17:42       ` Eric W. Biederman
2016-09-21 19:00         ` Jeremy Allison
2016-09-21 21:08         ` Andreas Grünbacher
2016-09-21 21:28   ` Andreas Grünbacher
2016-09-23  9:01     ` Miklos Szeredi
2016-09-23  9:15       ` Andreas Grünbacher

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=20160921134156.GA55138@ubuntu-hedt \
    --to=seth.forshee@canonical.com \
    --cc=Nikolaus@rath.org \
    --cc=agruenba@redhat.com \
    --cc=ebiederm@xmission.com \
    --cc=fuse-devel@lists.sourceforge.net \
    --cc=jean-pierre.andre@wanadoo.fr \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=mtheall@us.ibm.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).