From: Scott Mayhew <smayhew@redhat.com>
To: trond.myklebust@primarydata.com, anna.schumaker@netapp.com
Cc: linux-nfs@vger.kernel.org
Subject: [PATCH] nfs: override uid and gid for exclusive creates in nfs3_proc_create
Date: Fri, 22 Sep 2017 16:15:51 -0400 [thread overview]
Message-ID: <20170922201551.15222-1-smayhew@redhat.com> (raw)
RFC 1813 section 3.3.8 states
Once the client has performed a successful exclusive
create, it must issue a SETATTR to set the correct file
attributes. Until it does so, it should not rely upon any
of the file attributes, since the server implementation
may need to overload file metadata to store the verifier.
HP-UX expects the client to send the uid and gid in the post-create
setattr for exclusive creates. Customers are sometimes seeing bogus
values because the Linux NFS client is only updating the atime and
mtime.
Signed-off-by: Scott Mayhew <smayhew@redhat.com>
---
fs/nfs/nfs3proc.c | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/fs/nfs/nfs3proc.c b/fs/nfs/nfs3proc.c
index d1e87ec..4d77d2d 100644
--- a/fs/nfs/nfs3proc.c
+++ b/fs/nfs/nfs3proc.c
@@ -370,6 +370,13 @@ nfs3_proc_create(struct inode *dir, struct dentry *dentry, struct iattr *sattr,
if (data->arg.create.createmode == NFS3_CREATE_EXCLUSIVE) {
dprintk("NFS call setattr (post-create)\n");
+ sattr->ia_uid = current_fsuid();
+ sattr->ia_valid |= ATTR_UID;
+ if (dir->i_mode & S_ISGID)
+ sattr->ia_gid = dir->i_gid;
+ else
+ sattr->ia_gid = current_fsgid();
+ sattr->ia_valid |= ATTR_GID;
if (!(sattr->ia_valid & ATTR_ATIME_SET))
sattr->ia_valid |= ATTR_ATIME;
if (!(sattr->ia_valid & ATTR_MTIME_SET))
--
2.9.5
next reply other threads:[~2017-09-22 20:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-22 20:15 Scott Mayhew [this message]
2017-09-22 21:18 ` [PATCH] nfs: override uid and gid for exclusive creates in nfs3_proc_create Trond Myklebust
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=20170922201551.15222-1-smayhew@redhat.com \
--to=smayhew@redhat.com \
--cc=anna.schumaker@netapp.com \
--cc=linux-nfs@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.