Chuck Lever 5bbaed525e NFSD: Remove NFSERR_EAGAIN ... [ Upstream commit c6c209ceb87f64a6ceebe61761951dcbbf4a0baa ] 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 f4e44b3933 ("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: f4e44b3933 ("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: Sasha Levin <sashal@kernel.org> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>		2026-01-17 16:39:33 +01:00
..
events	softirq: Add trace points for tasklet entry/exit	2025-12-07 06:12:34 +09:00
misc	NFSD: Remove NFSERR_EAGAIN	2026-01-17 16:39:33 +01:00
stages	tracing: Remove pointer (asterisk) and brackets from cpumask_t field	2025-05-02 07:47:10 +02:00
bpf_probe.h	tracing: Add __cpumask to denote a trace event field that is a cpumask_t	2025-05-02 07:46:49 +02:00
define_custom_trace.h
define_trace.h
perf.h	tracing: Add __cpumask to denote a trace event field that is a cpumask_t	2025-05-02 07:46:49 +02:00
syscall.h
trace_custom_events.h
trace_events.h	tracing/ftrace: disable preemption in syscall probe	2024-12-14 19:54:45 +01:00