diff options
| author | NeilBrown <neilb@suse.de> | 2019-11-28 13:56:43 +1100 |
|---|---|---|
| committer | J. Bruce Fields <bfields@redhat.com> | 2019-11-30 14:59:52 -0500 |
| commit | 466e16f0920f3ffdfa49713212fa334fb3dc08f1 (patch) | |
| tree | fce5a8414513e8b4c7587d7f8f711e278b8b89ee /fs/nfsd/xdr4cb.h | |
| parent | a25e3726b32c746c0098125d4c7463bb84df72bb (diff) | |
| download | linux-466e16f0920f3ffdfa49713212fa334fb3dc08f1.tar.gz linux-466e16f0920f3ffdfa49713212fa334fb3dc08f1.tar.bz2 linux-466e16f0920f3ffdfa49713212fa334fb3dc08f1.zip | |
nfsd: check for EBUSY from vfs_rmdir/vfs_unink.
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.
Signed-off-by: NeilBrown <neilb@suse.de>
Signed-off-by: J. Bruce Fields <bfields@redhat.com>
Diffstat (limited to 'fs/nfsd/xdr4cb.h')
0 files changed, 0 insertions, 0 deletions