NFSv4.2: Don't send mode again in post-EXCLUSIVE4_1 SETATTR with umask
authorBenjamin Coddington <bcodding@redhat.com>
Fri, 2 Jun 2017 15:21:34 +0000 (11:21 -0400)
committerTrond Myklebust <trond.myklebust@primarydata.com>
Mon, 5 Jun 2017 16:23:15 +0000 (12:23 -0400)
commit501e7a4689378f8b1690089bfdd4f1e12ec22903
tree46df650388e7118f33780997d6d03b1599ae6b42
parent3c2993b8c6143d8a5793746a54eba8f86f95240f
NFSv4.2: Don't send mode again in post-EXCLUSIVE4_1 SETATTR with umask

Now that we have umask support, we shouldn't re-send the mode in a SETATTR
following an exclusive CREATE, or we risk having the same problem fixed in
commit 5334c5bdac92 ("NFS: Send attributes in OPEN request for
NFS4_CREATE_EXCLUSIVE4_1"), which is that files with S_ISGID will have that
bit stripped away.

Signed-off-by: Benjamin Coddington <bcodding@redhat.com>
Fixes: dff25ddb4808 ("nfs: add support for the umask attribute")
Cc: stable@vger.kernel.org # v4.10+
Signed-off-by: Trond Myklebust <trond.myklebust@primarydata.com>
fs/nfs/nfs4proc.c