From: Jeff Layton <jlayton@kernel.org>
To: trondmy@kernel.org, linux-nfs@vger.kernel.org
Cc: Josef Bacik <josef@toxicpanda.com>,
Benjamin Coddington <bcodding@redhat.com>
Subject: Re: [PATCH v3 4/6] NFSv4: Further cleanups to shutdown loops
Date: Tue, 25 Mar 2025 20:17:25 -0400 [thread overview]
Message-ID: <11be517780fadad1473a044c182648a131c874b5.camel@kernel.org> (raw)
In-Reply-To: <668e25098cb97187d084d5fa2916ddd4d2a68e00.1742941932.git.trond.myklebust@hammerspace.com>
On Tue, 2025-03-25 at 18:35 -0400, trondmy@kernel.org wrote:
> From: Trond Myklebust <trond.myklebust@hammerspace.com>
>
> Replace the tests for the RPC client being shut down with tests for
> whether the nfs_client is in an error state.
>
> Signed-off-by: Trond Myklebust <trond.myklebust@hammerspace.com>
> ---
> fs/nfs/nfs4proc.c | 2 +-
> fs/nfs/nfs4state.c | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/fs/nfs/nfs4proc.c b/fs/nfs/nfs4proc.c
> index 889511650ceb..50be54e0f578 100644
> --- a/fs/nfs/nfs4proc.c
> +++ b/fs/nfs/nfs4proc.c
> @@ -9580,7 +9580,7 @@ static void nfs41_sequence_call_done(struct rpc_task *task, void *data)
> return;
>
> trace_nfs4_sequence(clp, task->tk_status);
> - if (task->tk_status < 0 && !task->tk_client->cl_shutdown) {
> + if (task->tk_status < 0 && clp->cl_cons_state >= 0) {
> dprintk("%s ERROR %d\n", __func__, task->tk_status);
> if (refcount_read(&clp->cl_count) == 1)
> return;
> diff --git a/fs/nfs/nfs4state.c b/fs/nfs/nfs4state.c
> index 542cdf71229f..f1f7eaa97973 100644
> --- a/fs/nfs/nfs4state.c
> +++ b/fs/nfs/nfs4state.c
> @@ -1198,7 +1198,7 @@ void nfs4_schedule_state_manager(struct nfs_client *clp)
> struct rpc_clnt *clnt = clp->cl_rpcclient;
> bool swapon = false;
>
> - if (clnt->cl_shutdown)
> + if (clp->cl_cons_state < 0)
> return;
>
> set_bit(NFS4CLNT_RUN_MANAGER, &clp->cl_state);
This should probably also have:
Fixes: 6ad477a69ad8 ("NFSv4: Clean up some shutdown loops")
...but otherwise this looks good to me.
Reviewed-by: Jeff Layton <jlayton@kernel.org>
next prev parent reply other threads:[~2025-03-26 0:17 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-25 22:35 [PATCH v3 0/6] Ensure that ENETUNREACH terminates state recovery trondmy
2025-03-25 22:35 ` [PATCH v3 1/6] SUNRPC: rpcbind should never reset the port to the value '0' trondmy
2025-03-26 10:43 ` Benjamin Coddington
2025-03-25 22:35 ` [PATCH v3 2/6] SUNRPC: rpc_clnt_set_transport() must not change the autobind setting trondmy
2025-03-26 10:43 ` Benjamin Coddington
2025-03-25 22:35 ` [PATCH v3 3/6] NFS: Shut down the nfs_client only after all the superblocks trondmy
2025-03-26 0:15 ` Jeff Layton
2025-03-26 0:37 ` Trond Myklebust
2025-03-26 10:07 ` Benjamin Coddington
2025-03-25 22:35 ` [PATCH v3 4/6] NFSv4: Further cleanups to shutdown loops trondmy
2025-03-26 0:17 ` Jeff Layton [this message]
2025-03-26 10:13 ` Jeff Layton
2025-03-26 10:46 ` Benjamin Coddington
2025-03-26 18:11 ` Trond Myklebust
2025-03-26 18:21 ` Jeff Layton
2025-03-26 18:24 ` Trond Myklebust
2025-03-27 0:35 ` Jeff Layton
2025-03-25 22:35 ` [PATCH v3 5/6] NFSv4: clp->cl_cons_state < 0 signifies an invalid nfs_client trondmy
2025-03-26 0:17 ` Jeff Layton
2025-03-26 10:46 ` Benjamin Coddington
2025-03-25 22:35 ` [PATCH v3 6/6] NFSv4: Treat ENETUNREACH errors as fatal for state recovery trondmy
2025-03-26 10:39 ` Benjamin Coddington
2025-03-26 11:18 ` Jeff Layton
2025-03-26 13:10 ` Trond Myklebust
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=11be517780fadad1473a044c182648a131c874b5.camel@kernel.org \
--to=jlayton@kernel.org \
--cc=bcodding@redhat.com \
--cc=josef@toxicpanda.com \
--cc=linux-nfs@vger.kernel.org \
--cc=trondmy@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