From: Trond Myklebust <trondmy@hammerspace.com>
To: "linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Cc: "josef@toxicpanda.com" <josef@toxicpanda.com>,
"jlayton@kernel.org" <jlayton@kernel.org>
Subject: Re: [PATCH 4/4] NFSv4: Treat ENETUNREACH errors as fatal for state recovery
Date: Tue, 25 Mar 2025 11:36:27 +0000 [thread overview]
Message-ID: <7920f2e437aef041d54568097ad29a7b945588c1.camel@hammerspace.com> (raw)
In-Reply-To: <4855d263e403a8b56738f2f630954348718d7cc5.1742863168.git.trond.myklebust@hammerspace.com>
On Mon, 2025-03-24 at 20:46 -0400, trondmy@kernel.org wrote:
> From: Trond Myklebust <trond.myklebust@hammerspace.com>
>
> 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.
>
> Signed-off-by: Trond Myklebust <trond.myklebust@hammerspace.com>
> ---
> fs/nfs/nfs4state.c | 10 +++++++++-
> 1 file changed, 9 insertions(+), 1 deletion(-)
>
> diff --git a/fs/nfs/nfs4state.c b/fs/nfs/nfs4state.c
> index 738eb2789266..629578dd4a42 100644
> --- a/fs/nfs/nfs4state.c
> +++ b/fs/nfs/nfs4state.c
> @@ -2739,7 +2739,15 @@ static void nfs4_state_manager(struct
> nfs_client *clp)
> 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, status);
Actually, that probably needs to be nfs_mark_client_ready(clp, -EIO) in
order to make the return value a fatal I/O error.
> + break;
> + default:
> + ssleep(1);
> + break;
> + }
> out_drain:
> memalloc_nofs_restore(memflags);
> nfs4_end_drain_session(clp);
--
Trond Myklebust
Linux NFS client maintainer, Hammerspace
trond.myklebust@hammerspace.com
prev parent reply other threads:[~2025-03-25 11:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-25 0:46 [PATCH 0/4] Ensure that ENETUNREACH terminates state recovery trondmy
2025-03-25 0:46 ` [PATCH 1/4] SUNRPC: rpcbind should never reset the port to the value '0' trondmy
2025-03-25 0:46 ` [PATCH 2/4] SUNRPC: rpc_clnt_set_transport() must not change the autobind setting trondmy
2025-03-25 0:46 ` [PATCH 3/4] NFSv4: clp->cl_cons_state < 0 signifies an invalid nfs_client trondmy
2025-03-25 0:46 ` [PATCH 4/4] NFSv4: Treat ENETUNREACH errors as fatal for state recovery trondmy
2025-03-25 11:36 ` Trond Myklebust [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=7920f2e437aef041d54568097ad29a7b945588c1.camel@hammerspace.com \
--to=trondmy@hammerspace.com \
--cc=jlayton@kernel.org \
--cc=josef@toxicpanda.com \
--cc=linux-nfs@vger.kernel.org \
/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