NFSv4: Treat ENETUNREACH errors as fatal for state recovery

[ Upstream commit 0af5fb5ed3d2fd9e110c6112271f022b744a849a ]

If a containerised process is killed and causes an ENETUNREACH or
ENETDOWN error to be propagated to the state manager, then mark the
nfs_client as being dead so that we don't loop in functions that are
expecting recovery to succeed.

Reviewed-by: Jeff Layton <jlayton@kernel.org>
Reviewed-by: Benjamin Coddington <bcodding@redhat.com>
Signed-off-by: Trond Myklebust <trond.myklebust@hammerspace.com>
Signed-off-by: Sasha Levin <sashal@kernel.org>
This commit is contained in:
Trond Myklebust
2025-03-24 20:35:33 -04:00
committed by Greg Kroah-Hartman
parent ee68e068cf
commit 6b8beb8104

View File

@@ -2741,7 +2741,15 @@ out_error:
pr_warn_ratelimited("NFS: state manager%s%s failed on NFSv4 server %s"
" with error %d\n", section_sep, section,
clp->cl_hostname, -status);
ssleep(1);
switch (status) {
case -ENETDOWN:
case -ENETUNREACH:
nfs_mark_client_ready(clp, -EIO);
break;
default:
ssleep(1);
break;
}
out_drain:
memalloc_nofs_restore(memflags);
nfs4_end_drain_session(clp);