From: "J. Bruce Fields" <bfields@fieldses.org>
To: Nico Williams <nico@cryptonector.com>
Cc: "Haynes, Tom" <thomas@netapp.com>,
linux-nfs@vger.kernel.org, nfsv4@ietf.org
Subject: Re: [nfsv4] Constructing a NFSv4 ACL from POSIX mode bits
Date: Tue, 24 Jul 2012 16:09:32 -0400 [thread overview]
Message-ID: <20120724200932.GM8570@fieldses.org> (raw)
In-Reply-To: <CAK3OfOji009CP88tDNOp-nvdPBkvp0oKfJUqhO_TYuZktwhUCg@mail.gmail.com>
On Tue, Jul 24, 2012 at 03:00:57PM -0500, Nico Williams wrote:
> On Tue, Jul 24, 2012 at 2:33 PM, Haynes, Tom <thomas@netapp.com> wrote:
> > Bruce,
> >
> > In looking at http://tools.ietf.org/html/draft-ietf-nfsv4-acl-mapping-05, it
> > states that when mapping the write bit, only for the owner do we set
> > ACE4_WRITE_ACL.
> >
> > Back in version 00, it is open as to whether we can also set it for the
> > group and other if they have the write bit set.
> >
> > I looked back at the NFSv4 WG aliases and I see some discussion from Lisa
> > on how Solaris only ever sets it for the owner due to POSIX restrictions
> > via chmod(). So, now I know how another server does it.
>
> This has changed. I wrote this up here:
>
> http://cryptonector.com/2011/11/zfs-aclchmod-interactions-in-solaris-11/
>
> IIRC all ACEs for anything other than OWNER@ (or a user of the same
> name/ID) contribute to the group bits of the mode, the EVERYONE@ entry
> contributes to the world bits of the mode, and the OWNER@ and/or user
> ACEs for the owner name/ID contribute to the owner bits of the mode.
>
> The new scheme is really much simpler and more natural than everything
> else tried before.
Sounds reasonable.
But Tom was asking above only about ACE4_WRITE_ACL. And possibly only
in the legacy case. (Does ZFS have a real ACE4_WRITE_ACL bit?)
--b.
next prev parent reply other threads:[~2012-07-24 20:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-24 19:33 Constructing a NFSv4 ACL from POSIX mode bits Haynes, Tom
2012-07-24 19:53 ` J. Bruce Fields
2012-07-24 20:00 ` [nfsv4] " Nico Williams
2012-07-24 20:09 ` J. Bruce Fields [this message]
2012-07-24 20:29 ` Nico Williams
2012-07-25 13:29 ` 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=20120724200932.GM8570@fieldses.org \
--to=bfields@fieldses.org \
--cc=linux-nfs@vger.kernel.org \
--cc=nfsv4@ietf.org \
--cc=nico@cryptonector.com \
--cc=thomas@netapp.com \
/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).