From: bfields@fieldses.org (J. Bruce Fields)
To: Rik Theys <Rik.Theys@esat.kuleuven.be>
Cc: linux-nfs@vger.kernel.org
Subject: Re: status of NFS4 acls and umask
Date: Thu, 10 Jan 2019 15:29:13 -0500 [thread overview]
Message-ID: <20190110202913.GD15492@fieldses.org> (raw)
In-Reply-To: <0dd5344e-231f-1670-ffe1-5974b57dbaf3@esat.kuleuven.be>
On Tue, Dec 11, 2018 at 02:11:59PM +0100, Rik Theys wrote:
> In https://www.spinics.net/lists/linux-nfs/msg27799.html from 2011, Jeff
> Layton describes how/why an NFSv4 ACL does not override the umask like a
> posix ACL does. It mentions that it did not work back then and that
> something might be done about that.
>
> What is the status now? When I look at the CentOS 7.6 client/server it
> seems this is still not implemented. Is this fixed in newer upstream
> versions? If not, are there any plans on finding a solution?
I'ts fixed if your NFSv4.2 client and server implement
https://tools.ietf.org/html/rfc8275, which upstream linux client and
server now do. For RHEL I believe that change went into 7.4. If that's
not working for you, you may need to check that the protocol version is
4.2.
--b.
prev parent reply other threads:[~2019-01-10 20:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-11 13:11 status of NFS4 acls and umask Rik Theys
2019-01-10 20:29 ` J. Bruce Fields [this message]
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=20190110202913.GD15492@fieldses.org \
--to=bfields@fieldses.org \
--cc=Rik.Theys@esat.kuleuven.be \
--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