From: "J. Bruce Fields" <bfields@redhat.com>
To: Trond Myklebust <trond.myklebust@primarydata.com>,
Anna Schumaker <schumakeranna@gmail.com>
Cc: linux-nfs@vger.kernel.org, Andreas Gruenbacher <agruenba@redhat.com>
Subject: NFSv4.2 mode_umask support
Date: Wed, 23 Nov 2016 15:41:38 -0500 [thread overview]
Message-ID: <1479933700-5743-1-git-send-email-bfields@redhat.com> (raw)
Resending--can we get any opinions on these?
The following patches allow the umask to be ignored in the presence of
inheritable NFSv4 ACLs. Otherwise inheritable ACLs can be rendered
mostly useless whenever the umask masks out group bits.
This solves a problem we've seen complaints about for some time, both
upstream and from RHEL users.
The new protocol has been discussed in the IETF working group and is
documented at:
https://tools.ietf.org/html/draft-ietf-nfsv4-umask-02
It's unlikely that we'll discover problems requiring an incompatible
change, so I think we should consider this for 4.10.
--b.
next reply other threads:[~2016-11-23 20:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-23 20:41 J. Bruce Fields [this message]
2016-11-23 20:41 ` [PATCH 1/2] nfs: add support for the umask attribute J. Bruce Fields
2016-12-01 22:07 ` J. Bruce Fields
2016-12-02 13:12 ` Andreas Gruenbacher
2016-12-02 16:47 ` J. Bruce Fields
2017-02-01 21:31 ` Olga Kornievskaia
2017-02-01 22:37 ` J. Bruce Fields
2017-02-01 22:44 ` Andreas Gruenbacher
2017-02-02 16:49 ` Olga Kornievskaia
2016-11-23 20:41 ` [PATCH 2/2] nfsd: " J. Bruce Fields
-- strict thread matches above, loose matches on Subject: below --
2016-12-03 3:53 NFSv4.2 mode_umask support J. Bruce Fields
2016-12-09 20:59 ` 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=1479933700-5743-1-git-send-email-bfields@redhat.com \
--to=bfields@redhat.com \
--cc=agruenba@redhat.com \
--cc=linux-nfs@vger.kernel.org \
--cc=schumakeranna@gmail.com \
--cc=trond.myklebust@primarydata.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).