From: "J. Bruce Fields" <bfields@fieldses.org>
To: "zhengbin (A)" <zhengbin13@huawei.com>
Cc: jlayton@kernel.org, linux-nfs@vger.kernel.org,
houtao1@huawei.com, zhaohongjiang@huawei.com
Subject: Re: [PATCH] nfsd: Return EPERM on utime/utimes/lutimes calls instead of EACCESS in some cases
Date: Tue, 4 Dec 2018 20:37:17 -0500 [thread overview]
Message-ID: <20181205013717.GA6093@fieldses.org> (raw)
In-Reply-To: <e3073b92-1eab-78f5-09ae-629e6496fac4@huawei.com>
On Wed, Dec 05, 2018 at 09:04:22AM +0800, zhengbin (A) wrote:
> thanks,
> >>> As the man(3) page for utime/utimes/lutimes, EPERM is returned
>
> -------->this should be As the man page for utime/utimes/lutimes, my little mistake. utime/utimes are man(2), lutimes is man(3)
>
> I send v2 patch?Or when you apply, help modify it?
Does this look OK?
--b.
commit eb6d67589750
Author: zhengbin <zhengbin13@huawei.com>
Date: Fri Nov 30 16:04:25 2018 +0800
nfsd: Return EPERM, not EACCES, in some SETATTR cases
As the man(2) page for utime/utimes states, EPERM is returned when the
second parameter of utime/utimes/lutimes 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>
diff --git a/fs/nfsd/vfs.c b/fs/nfsd/vfs.c
index eb67098117b4..9824e32b2f23 100644
--- a/fs/nfsd/vfs.c
+++ b/fs/nfsd/vfs.c
@@ -396,10 +396,23 @@ nfsd_setattr(struct svc_rqst *rqstp, struct svc_fh *fhp, struct iattr *iap,
bool get_write_count;
bool size_change = (iap->ia_valid & ATTR_SIZE);
- if (iap->ia_valid & (ATTR_ATIME | ATTR_MTIME | ATTR_SIZE))
+ if (iap->ia_valid & ATTR_SIZE) {
accmode |= NFSD_MAY_WRITE|NFSD_MAY_OWNER_OVERRIDE;
- if (iap->ia_valid & ATTR_SIZE)
ftype = S_IFREG;
+ }
+
+ /*
+ * If utimes(2) and friends are called with times not NULL, we should
+ * not set NFSD_MAY_WRITE bit. Otherwise fh_verify->nfsd_permission
+ * will return EACCESS, when the caller's effective UID does not match
+ * the owner of the file, and the caller is not privileged. In this
+ * situation, we should return EPERM(notify_change will return this).
+ */
+ if (iap->ia_valid & (ATTR_ATIME | ATTR_MTIME)) {
+ accmode |= NFSD_MAY_OWNER_OVERRIDE;
+ if (!(iap->ia_valid & (ATTR_ATIME_SET | ATTR_MTIME_SET)))
+ accmode |= NFSD_MAY_WRITE;
+ }
/* Callers that do fh_verify should do the fh_want_write: */
get_write_count = !fhp->fh_dentry;
next prev parent reply other threads:[~2018-12-05 1:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-30 7:51 [PATCH] nfsd: Return EPERM on utime/utimes/lutimes calls instead of EACCESS in some cases zhengbin
2018-12-03 8:36 ` zhengbin (A)
2018-12-04 20:13 ` J. Bruce Fields
2018-12-05 1:04 ` zhengbin (A)
2018-12-05 1:37 ` J. Bruce Fields [this message]
2018-12-05 1:43 ` zhengbin (A)
2018-12-05 1:49 ` J. Bruce Fields
-- strict thread matches above, loose matches on Subject: below --
2018-11-30 8:04 zhengbin
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=20181205013717.GA6093@fieldses.org \
--to=bfields@fieldses.org \
--cc=houtao1@huawei.com \
--cc=jlayton@kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=zhaohongjiang@huawei.com \
--cc=zhengbin13@huawei.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox