From: "J. Bruce Fields" <bfields@fieldses.org>
To: Drew Leske <drew.leske@computecanada.ca>
Cc: linux-nfs@vger.kernel.org
Subject: Re: Non-root chown, NFSv4 ACLs
Date: Thu, 7 Dec 2017 18:15:06 -0500 [thread overview]
Message-ID: <20171207231506.GB7527@fieldses.org> (raw)
In-Reply-To: <F6FBCAE9-DB8D-4965-B761-58ACDF245BC3@computecanada.ca>
On Thu, Dec 07, 2017 at 02:54:22PM -0800, Drew Leske wrote:
> The remaining question for me then is around the NFSv4 ACL and the
> ownership change permission, and whether I should be able to get that
> to work, especially on a stock system.
No. When you set an ACL, the server just translates that ACL to the
closet POSIX ACL it can find. And the filesystem code just enforces
that POSIX ACL. POSIX ACLs have no equivalent to WRITE_OWNER. I can't
remember what the code in fs/nfsd/nfs4acl.c does--the only choices would
be to either ignore the bit or fail, I think it does the former.
(In theory knfsd could store the full v4 ACL in an extended attribute
and do its own enforcement on the side--I think Samba can do something
like this. This seems complicated to me and I'd rather add richacl
support to the filesystems, but that effort has stalled.)
> I know there are some issues
> with mapping NFSv4 ACLs to so-called “POSIX” ACLs, but I didn’t see
> anything in the documentation to suggest it isn’t implemented. Should
> I expect this to work without installing the richacls software?
You'd have to actually apply the richacls kernel patch. I think you'd
find that more trouble than it's worth.
--b.
next prev parent reply other threads:[~2017-12-07 23:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-07 19:43 Non-root chown, NFSv4 ACLs Drew Leske
2017-12-07 20:05 ` Frank Filz
2017-12-07 20:21 ` Drew Leske
2017-12-07 21:34 ` J. Bruce Fields
2017-12-07 22:54 ` Drew Leske
2017-12-07 23:15 ` J. Bruce Fields [this message]
2017-12-09 0:53 ` Drew Leske
2017-12-13 20:28 ` Drew Leske
2017-12-19 17:18 ` 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=20171207231506.GB7527@fieldses.org \
--to=bfields@fieldses.org \
--cc=drew.leske@computecanada.ca \
--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).