From: "J. Bruce Fields" <bfields@fieldses.org>
To: Ross Lagerwall <rosslagerwall@gmail.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH] nfsd3: Check write permission after checking existence
Date: Mon, 11 Aug 2014 15:08:38 -0400 [thread overview]
Message-ID: <20140811190838.GE9095@fieldses.org> (raw)
In-Reply-To: <1407591840-19080-1-git-send-email-rosslagerwall@gmail.com>
On Sat, Aug 09, 2014 at 02:44:00PM +0100, Ross Lagerwall wrote:
> When creating a file that already exists in a read-only directory with
> O_EXCL, the NFSv3 server returns EACCES rather than EEXIST (which local
> files and the NFSv4 server return). Fix this by checking the MAY_CREATE
> permission only if the file does not exist. Since this already happens
> in do_nfsd_create, the check in nfsd3_proc_create can simply be removed.
Thanks.
>From a look at the history I believe the server has behaved this way
since the beginning. Is this creating a practical problem for you? How
did you notice it?
Inclined to apply it just for consistency as you suggest. And because
it removes some unnecessary code. But as a low priority: for 3.18 and
not stable.
--b.
>
> Signed-off-by: Ross Lagerwall <rosslagerwall@gmail.com>
> ---
> fs/nfsd/nfs3proc.c | 5 -----
> 1 file changed, 5 deletions(-)
>
> diff --git a/fs/nfsd/nfs3proc.c b/fs/nfsd/nfs3proc.c
> index 4012899..8ebd4ac 100644
> --- a/fs/nfsd/nfs3proc.c
> +++ b/fs/nfsd/nfs3proc.c
> @@ -227,11 +227,6 @@ nfsd3_proc_create(struct svc_rqst *rqstp, struct nfsd3_createargs *argp,
> newfhp = fh_init(&resp->fh, NFS3_FHSIZE);
> attr = &argp->attrs;
>
> - /* Get the directory inode */
> - nfserr = fh_verify(rqstp, dirfhp, S_IFDIR, NFSD_MAY_CREATE);
> - if (nfserr)
> - RETURN_STATUS(nfserr);
> -
> /* Unfudge the mode bits */
> attr->ia_mode &= ~S_IFMT;
> if (!(attr->ia_valid & ATTR_MODE)) {
> --
> 2.0.3
>
next prev parent reply other threads:[~2014-08-11 19:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-09 13:44 [PATCH] nfsd3: Check write permission after checking existence Ross Lagerwall
2014-08-11 19:08 ` J. Bruce Fields [this message]
2014-08-11 20:28 ` Ross Lagerwall
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=20140811190838.GE9095@fieldses.org \
--to=bfields@fieldses.org \
--cc=linux-nfs@vger.kernel.org \
--cc=rosslagerwall@gmail.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;
as well as URLs for NNTP newsgroup(s).