From: "Paul B. Henson" <henson@acm.org>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: linux-nfs@vger.kernel.org
Subject: Re: nfs4-acl-tools 0.3.5
Date: Wed, 22 Aug 2018 18:11:20 -0700 [thread overview]
Message-ID: <2be55f4f-4c9c-9ee1-72f4-b21e37336b6e@acm.org> (raw)
In-Reply-To: <20180822194620.GA25562@fieldses.org>
On 8/22/2018 12:46 PM, J. Bruce Fields wrote:
>
>> I'll strip them out and send you a patch soon; hopefully it won't
>> take 10 more years to show up in a release :).
>
> OK, great, thanks.
Patch sent; it was pretty trivial, hopefully it will suffice.
> I can't take knfsd patches to support something that only an
> out-of-tree filesystem cares about.
Hmm, I hadn't considered that, but I understand the position.
> Looks like ZFS has pretty much no chance of going upstream.
Yah, GPL, CDDL, they don't get along :(.
> You could try to port them to some other filesystem (xfs, ext4).
The ZFS on Linux port already supports the standard POSIX ACL. I'm
curious, do those work with the NFS server? Does something specifically
need to be done individually for each file system, or if it supports the
standard extended attribute does any file system (including an out of
tree file system) automatically function?
> But the attempt to implement rich ACLs (which are pretty similar)
> seemed to get vetoed for reasons I don't completely understand, and I
> don't see why this would fare any better.
While they have different implementation details, NFSv4 ACLs and rich
ACLs seem to have compatible expression formats. If they ever do get
implemented, I'd be able to switch from the somewhat inefficient
system.nfs4 extended attribute interface between the kernel and user
space for ZFS ACLs to a rich ACL API... And if the NFS server would
simply work with any file system that exported a standard rich ACL,
maybe ZFS would work then.
> So I think you'd be stuck carrying your own out-of-tree patches for
> it.
Hmm, that would greatly reduce the size of the user base; most
distributions now make ZFS available via their packaging systems, but I
don't know how many would be willing to include an extra ZFS specific
kernel patch for NFS service.
Thanks again…
next prev parent reply other threads:[~2018-08-23 4:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-07 19:37 nfs4-acl-tools 0.3.4 J. Bruce Fields
2018-08-21 16:51 ` nfs4-acl-tools 0.3.5 J. Bruce Fields
2018-08-21 23:44 ` Paul B. Henson
2018-08-22 0:33 ` J. Bruce Fields
2018-08-22 1:18 ` Paul B. Henson
2018-08-22 15:12 ` J. Bruce Fields
2018-08-22 19:28 ` Paul B. Henson
2018-08-22 19:46 ` J. Bruce Fields
2018-08-23 1:11 ` Paul B. Henson [this message]
2018-08-23 14:38 ` J. Bruce Fields
2018-08-23 19:41 ` Paul B. Henson
2018-08-24 5:51 ` Christoph Hellwig
2018-08-23 19:41 ` Paul B. Henson
2018-08-23 20:57 ` J. Bruce Fields
2018-08-24 0:50 ` Paul B. Henson
2018-08-24 15:26 ` J. Bruce Fields
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=2be55f4f-4c9c-9ee1-72f4-b21e37336b6e@acm.org \
--to=henson@acm.org \
--cc=bfields@fieldses.org \
--cc=linux-nfs@vger.kernel.org \
/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).