From: "J. Bruce Fields" <bfields@fieldses.org>
To: NeilBrown <neilb@suse.de>
Cc: Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH] nfsd: check for EBUSY from vfs_rmdir/vfs_unink.
Date: Sat, 30 Nov 2019 15:00:02 -0500 [thread overview]
Message-ID: <20191130200002.GB19460@fieldses.org> (raw)
In-Reply-To: <87imn4iu8k.fsf@notabene.neil.brown.name>
On Thu, Nov 28, 2019 at 01:56:43PM +1100, NeilBrown wrote:
>
> vfs_rmdir and vfs_unlink can return -EBUSY if the
> target is a mountpoint. This currently gets passed to
> nfserrno() by nfsd_unlink(), and that results in a WARNing,
> which is not user-friendly.
>
> Possibly the best NFSv4 error is NFS4ERR_FILE_OPEN, because
> there is a sense in which the object is currently in use
> by some other task. The Linux NFSv4 client will map this
> back to EBUSY, which is an added benefit.
>
> For NFSv3, the best we can do is probably NFS3ERR_ACCES, which isn't
> true, but is not less true than the other options.
Makes sense to me, thanks.--b.
>
> Signed-off-by: NeilBrown <neilb@suse.de>
> ---
> fs/nfsd/nfsd.h | 3 ++-
> fs/nfsd/vfs.c | 12 +++++++++++-
> 2 files changed, 13 insertions(+), 2 deletions(-)
>
> diff --git a/fs/nfsd/nfsd.h b/fs/nfsd/nfsd.h
> index af2947551e9c..57b93d95fa5c 100644
> --- a/fs/nfsd/nfsd.h
> +++ b/fs/nfsd/nfsd.h
> @@ -280,7 +280,8 @@ void nfsd_lockd_shutdown(void);
> #define nfserr_union_notsupp cpu_to_be32(NFS4ERR_UNION_NOTSUPP)
> #define nfserr_offload_denied cpu_to_be32(NFS4ERR_OFFLOAD_DENIED)
> #define nfserr_wrong_lfs cpu_to_be32(NFS4ERR_WRONG_LFS)
> -#define nfserr_badlabel cpu_to_be32(NFS4ERR_BADLABEL)
> +#define nfserr_badlabel cpu_to_be32(NFS4ERR_BADLABEL)
> +#define nfserr_file_open cpu_to_be32(NFS4ERR_FILE_OPEN)
>
> /* error codes for internal use */
> /* if a request fails due to kmalloc failure, it gets dropped.
> diff --git a/fs/nfsd/vfs.c b/fs/nfsd/vfs.c
> index bd0a385df3fc..fa2acb6a3b5c 100644
> --- a/fs/nfsd/vfs.c
> +++ b/fs/nfsd/vfs.c
> @@ -1809,7 +1809,17 @@ nfsd_unlink(struct svc_rqst *rqstp, struct svc_fh *fhp, int type,
> out_drop_write:
> fh_drop_write(fhp);
> out_nfserr:
> - err = nfserrno(host_err);
> + if (host_err == -EBUSY) {
> + /* name is mounted-on. There is no perfect
> + * error status.
> + */
> + if (nfsd_v4client(rqstp))
> + err = nfserr_file_open;
> + else
> + err = nfserr_acces;
> + } else {
> + err = nfserrno(host_err);
> + }
> out:
> return err;
> }
> --
> 2.24.0
>
prev parent reply other threads:[~2019-11-30 20:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-28 2:56 [PATCH] nfsd: check for EBUSY from vfs_rmdir/vfs_unink NeilBrown
2019-11-30 20:00 ` J. Bruce Fields [this message]
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=20191130200002.GB19460@fieldses.org \
--to=bfields@fieldses.org \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@suse.de \
/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).