From: "Paul B. Henson" <henson@acm.org>
To: "J. Bruce Fields" <bfields@fieldses.org>, linux-nfs@vger.kernel.org
Subject: Re: nfs4-acl-tools 0.3.5
Date: Tue, 21 Aug 2018 16:44:38 -0700 [thread overview]
Message-ID: <5fa4b700-3d45-cda3-37ed-bdfbd427574d@acm.org> (raw)
In-Reply-To: <20180821165130.GA14413@fieldses.org>
On 8/21/2018 9:51 AM, J. Bruce Fields wrote:
> One more nfs4-acl-tools release. This removes the GUI, which appears to
I had recently posted an inquiry regarding the nfs4-acl-tools; I don't
believe I saw a response but if you are maintaining them perhaps you
might know?
I'm currently working on implementing support for the native NFSv4 ACL
in the ZFS on Linux port, using nfs4-acl-tools as the mechanism for
viewing and updating them. I noticed a discrepancy between the
definitions in the ZFS NFSv4 ACL include file versus the ones in the
nfs4-acl-tools headers.
Specifically, in zfs:
#define ACE_INHERITED_ACE 0x0080
#define ACE_OWNER 0x1000
#define ACE_GROUP 0x2000
#define ACE_EVERYONE 0x4000
Whereas in nfs4-acl-tools:
#define NFS4_ACE_OWNER 0x00000080
#define NFS4_ACE_GROUP 0x00000100
#define NFS4_ACE_EVERYONE 0x00000200
I'm not sure where these values came from, I don't see them in the NFSv4
RFC. Do you happen to have any idea where the values used in the
nfs4-acl-tools came from and why they might be different than those used
by zfs?
Thanks much…
next prev parent reply other threads:[~2018-08-22 3:07 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 [this message]
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
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=5fa4b700-3d45-cda3-37ed-bdfbd427574d@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).