From: "Paul B. Henson" <henson@acm.org>
To: linux-nfs@vger.kernel.org
Subject: nfs4-acl-tools vs ZFS NFSv4 based acl internals
Date: Thu, 16 Aug 2018 17:14:27 -0700 [thread overview]
Message-ID: <571bacd0-759d-af39-a998-d96f30ecb8e2@acm.org> (raw)
I'm currently working on getting the native NFSv4 based ZFS ACL working
in the zfs on linux port. As there isn't currently a kernel interface
for this type of ACL, I'm using the same system.nfs4_acl extended
attribute to interface touser space as the NFS client, and the
nfs4-acl-tools implementation to manage them.
I ran into an issue which I traced down to a discrepancy between the
definitions for the flags between ZFS and the nfs4-acl-tools package:
From zfs/acl.h:
#define ACE_INHERITED_ACE 0x0080
#define ACE_OWNER 0x1000
#define ACE_GROUP 0x2000
#define ACE_EVERYONE 0x4000
From nfs4-acl-tools:
#define NFS4_ACE_OWNER 0x00000080
#define NFS4_ACE_GROUP 0x00000100
#define NFS4_ACE_EVERYONE 0x00000200
Does anyone know why these are different? I couldn't find these defined
in the NFSv4 RFC, so I'm not sure where either side got the specific
values they are using. For now, I am mapping between the values as I go
between the zfs internals and the extended attribute values. However,
that is not ideal, particularly as it prevents passing the inherited ace
flag given the value conflicts between the two.
reply other threads:[~2018-08-17 3:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=571bacd0-759d-af39-a998-d96f30ecb8e2@acm.org \
--to=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).