]> git.ipfire.org Git - thirdparty/kernel/stable.git/commit
NFSD: Remove NFSERR_EAGAIN
authorChuck Lever <chuck.lever@oracle.com>
Wed, 10 Dec 2025 00:28:49 +0000 (19:28 -0500)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Sat, 17 Jan 2026 15:35:10 +0000 (16:35 +0100)
commit0f7fb819d63f3339c1a4eaf81d9edc28c34fca2b
tree6be8064937865390f4c92080bd2c34b64e5e24ee
parentdb78fa4b9f1fbedcb979b5d0c486d4f451ee7799
NFSD: Remove NFSERR_EAGAIN

commit c6c209ceb87f64a6ceebe61761951dcbbf4a0baa upstream.

I haven't found an NFSERR_EAGAIN in RFCs 1094, 1813, 7530, or 8881.
None of these RFCs have an NFS status code that match the numeric
value "11".

Based on the meaning of the EAGAIN errno, I presume the use of this
status in NFSD means NFS4ERR_DELAY. So replace the one usage of
nfserr_eagain, and remove it from NFSD's NFS status conversion
tables.

As far as I can tell, NFSERR_EAGAIN has existed since the pre-git
era, but was not actually used by any code until commit f4e44b393389
("NFSD: delay unmount source's export after inter-server copy
completed."), at which time it become possible for NFSD to return
a status code of 11 (which is not valid NFS protocol).

Fixes: f4e44b393389 ("NFSD: delay unmount source's export after inter-server copy completed.")
Cc: stable@vger.kernel.org
Reviewed-by: NeilBrown <neil@brown.name>
Reviewed-by: Jeff Layton <jlayton@kernel.org>
Signed-off-by: Chuck Lever <chuck.lever@oracle.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
fs/nfs_common/common.c
fs/nfsd/nfs4proc.c
fs/nfsd/nfsd.h
include/trace/misc/nfs.h
include/uapi/linux/nfs.h