[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <153861471803.30373.6184444014227748848.stgit@noble>
Date: Thu, 04 Oct 2018 11:02:43 +1000
From: NeilBrown <neilb@...e.com>
To: "J. Bruce Fields" <bfields@...ldses.org>,
Anna Schumaker <anna.schumaker@...app.com>,
Alexander Viro <viro@...iv.linux.org.uk>,
Trond Myklebust <trond.myklebust@...merspace.com>
Cc: Jan Harkes <jaharkes@...cmu.edu>, linux-nfs@...r.kernel.org,
Miklos Szeredi <miklos@...redi.hu>,
Jeff Layton <jlayton@...nel.org>, linux-kernel@...r.kernel.org,
linux-afs@...ts.infradead.org, David Howells <dhowells@...hat.com>,
coda@...cmu.edu, linux-fsdevel@...r.kernel.org,
Christoph Hellwig <hch@....de>
Subject: [PATCH 0/3] Fix regression in NFSv3 ACL setting
Commit 013cdf1088d7 ("nfs: use generic posix ACL infrastructure for v3
Posix ACLs") introduce a regression for NFSv3 ACL setting.
An owner should be able to set an ACL, but the new code tests for
ownership in a way that is not reliable for NFSv3. For NFSv3 the only
reliable test is to send the request to the server and see if it works.
The first patch introduces MAY_ACT_AS_OWNER and relies on the
filesystem to do the appropriate ownership test. This touches
several filesystems, hence the long 'Cc' list.
Following two patches are small code cleanups relating to this.
Thanks,
NeilBrown
---
NeilBrown (3):
VFS: introduce MAY_ACT_AS_OWNER
VFS: allow MAY_ flags to be easily extended.
NFSD - Use MAY_ACT_AS_OWNER
fs/afs/security.c | 10 ++++++++++
fs/attr.c | 12 +++++-------
fs/coda/dir.c | 10 ++++++++++
fs/fcntl.c | 2 +-
fs/fuse/dir.c | 10 ++++++++++
fs/namei.c | 9 +++++++++
fs/nfs/dir.c | 8 ++++++++
fs/nfsd/vfs.c | 11 ++++++-----
fs/nfsd/vfs.h | 33 ++++++++++++++++++---------------
fs/posix_acl.c | 2 +-
fs/xattr.c | 2 +-
include/linux/fs.h | 10 ++++++++++
12 files changed, 89 insertions(+), 30 deletions(-)
--
Signature
Powered by blists - more mailing lists