nfsd: Return EPERM, not EACCES, in some SETATTR cases
authorzhengbin <zhengbin13@huawei.com>
Fri, 30 Nov 2018 08:04:25 +0000 (16:04 +0800)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Sat, 21 Dec 2019 09:41:24 +0000 (10:41 +0100)
commit25a479768ace4161388e5d94e49c45db017fda3c
tree0f9e40f3859ed2cfbea85e0e3db3ac8263c13052
parent64954c8d093e8f29364e6c5b585bd23bdf86dfc1
nfsd: Return EPERM, not EACCES, in some SETATTR cases

[ Upstream commit 255fbca65137e25b12bced18ec9a014dc77ecda0 ]

As the man(2) page for utime/utimes states, EPERM is returned when the
second parameter of utime or utimes is not NULL, the caller's effective UID
does not match the owner of the file, and the caller is not privileged.

However, in a NFS directory mounted from knfsd, it will return EACCES
(from nfsd_setattr-> fh_verify->nfsd_permission).  This patch fixes
that.

Signed-off-by: zhengbin <zhengbin13@huawei.com>
Signed-off-by: J. Bruce Fields <bfields@redhat.com>
Signed-off-by: Sasha Levin <sashal@kernel.org>
fs/nfsd/vfs.c