From: "J. Bruce Fields" <bfields@fieldses.org>
To: Vyacheslav Dubeyko <slava@dubeyko.com>
Cc: linux-fsdevel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Christoph Hellwig <hch@infradead.org>,
Al Viro <viro@zeniv.linux.org.uk>,
Hin-Tak Leung <htl10@users.sourceforge.net>
Subject: Re: [PATCH v3 2/3] hfsplus: add implementation of the ACLs support
Date: Tue, 5 Mar 2013 11:32:23 -0500 [thread overview]
Message-ID: <20130305163223.GA14668@fieldses.org> (raw)
In-Reply-To: <1362466376.2572.25.camel@slavad-ubuntu>
On Tue, Mar 05, 2013 at 10:52:56AM +0400, Vyacheslav Dubeyko wrote:
> On Mon, 2013-03-04 at 16:26 -0500, J. Bruce Fields wrote:
> > On Sun, Mar 03, 2013 at 07:29:32PM +0400, Vyacheslav Dubeyko wrote:
> > > From: Vyacheslav Dubeyko <slava@dubeyko.com>
> > > Subject: [PATCH v3 2/3] hfsplus: add implementation of the ACLs support
> > >
> > > This patch adds implementation of the ACLs support for hfsplus driver.
> >
> > Much of this actually appears to have started as a cut-and-paste of
> > fs/nfsd/nfs4acl.c.
> >
> > Could you explain what you needed to change from the nfsd code?
> >
> > It looks like we should be able to share at least some of this code
> > instead of copying it. The posix<->NFSv4 ACL mapping is a bit tricky
> > and I'd prefer we not have to fix bugs in two different instances of it.
> >
>
> Yes, I totally agree with you. I used fs/nfsd/nfs4acl.c as a basis for
> implementation of ACLs support in hfsplus. But it was a first step
> because I can't used implemented in nfsd functionality without changes.
> The ACLs in hfsplus have some peculiarities (special raw ACLs
> representation and slightly special set of flags) and I needed to
> achieve first of all working implementation of ACLs support. Now it is
> done and I think over how to share common code between hfsplus and nfsd.
> Maybe it can be useful and for other drivers. As a preliminary vision, I
> think that we can have something like pair of files:
> include/linux/nfsv4_acl.h (declarations) and fs/nfsv4_acl.c
> (implementation). The implementation should share common code with
> possibility to implement specialized part functionality in the concrete
> driver.
Sure.
> > Also: have you looked at the latest rich ACL patches? That would
> > provide a native interface to NFSv4-like ACLs, which would really be
> > much more useful.
> >
>
> Could you point out about what patches you are talking? Maybe these
> patches correct my vision of sharing code between hfsplus and nfsd.
They implement NFSv4-like ACLs for ext4, and hook them up to nfs and
nfsd:
http://www.bestbits.at/richacl/
Ideally hfsplus would use the same interface. The translation wouldn't
be perfect, but it'd be easier than posix<->nfsv4.
The last review I can find is:
http://marc.info/?l=linux-fsdevel&m=131944979121959&w=2
which comes across as a rant, but I think there are some concrete things
to work on there that just need a volunteer to take on.
--b.
prev parent reply other threads:[~2013-03-05 16:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-03 15:29 [PATCH v3 2/3] hfsplus: add implementation of the ACLs support Vyacheslav Dubeyko
2013-03-04 21:26 ` J. Bruce Fields
2013-03-05 6:52 ` Vyacheslav Dubeyko
2013-03-05 16:32 ` J. Bruce Fields [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=20130305163223.GA14668@fieldses.org \
--to=bfields@fieldses.org \
--cc=akpm@linux-foundation.org \
--cc=hch@infradead.org \
--cc=htl10@users.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=slava@dubeyko.com \
--cc=viro@zeniv.linux.org.uk \
/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).