From: "J. Bruce Fields" <bfields@fieldses.org>
To: "Paul B. Henson" <henson@acm.org>
Cc: linux-nfs@vger.kernel.org
Subject: Re: nfs4-acl-tools 0.3.5
Date: Thu, 23 Aug 2018 10:38:35 -0400 [thread overview]
Message-ID: <20180823143835.GB1019@fieldses.org> (raw)
In-Reply-To: <2be55f4f-4c9c-9ee1-72f4-b21e37336b6e@acm.org>
On Wed, Aug 22, 2018 at 06:11:20PM -0700, Paul B. Henson wrote:
> >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?
Yes. Sort of. There's a sideband protocol for NFSv3 that supports them
pretty much as they are. NFSv4 only has NFSv4 ACLs, so we support them
by translating between "posix" and NFSv4 ACLs on the fly, and the
result can be a pain to use.
> 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?
Nothing special's required, it should be automatic.
--b.
next prev parent reply other threads:[~2018-08-23 18:08 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
2018-08-23 14:38 ` J. Bruce Fields [this message]
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=20180823143835.GB1019@fieldses.org \
--to=bfields@fieldses.org \
--cc=henson@acm.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).