All of lore.kernel.org
 help / color / mirror / Atom feed
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 3/6] NFS: Shut down the nfs_client only after all the superblocks
Date: Tue, 25 Mar 2025 20:15:21 -0400	[thread overview]
Message-ID: <ecccbc8fca9b057d018bb68acedfb47a6cf76550.camel@kernel.org> (raw)
In-Reply-To: <1cefd7cbadf0eaec5bae66e0870cdb89c7120070.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>
> 
> The nfs_client manages state for all the superblocks in the
> "cl_superblocks" list, so it must not be shut down until all of them are
> gone.
> 
> Fixes: 7d3e26a054c8 ("NFS: Cancel all existing RPC tasks when shutdown")
> Signed-off-by: Trond Myklebust <trond.myklebust@hammerspace.com>
> ---
>  fs/nfs/sysfs.c | 22 +++++++++++++++++++++-
>  1 file changed, 21 insertions(+), 1 deletion(-)
> 
> diff --git a/fs/nfs/sysfs.c b/fs/nfs/sysfs.c
> index b30401b2c939..37cb2b776435 100644
> --- a/fs/nfs/sysfs.c
> +++ b/fs/nfs/sysfs.c
> @@ -14,6 +14,7 @@
>  #include <linux/rcupdate.h>
>  #include <linux/lockd/lockd.h>
>  
> +#include "internal.h"
>  #include "nfs4_fs.h"
>  #include "netns.h"
>  #include "sysfs.h"
> @@ -228,6 +229,25 @@ static void shutdown_client(struct rpc_clnt *clnt)
>  	rpc_cancel_tasks(clnt, -EIO, shutdown_match_client, NULL);
>  }
>  
> +/*
> + * Shut down the nfs_client only once all the superblocks
> + * have been shut down.
> + */
> +static void shutdown_nfs_client(struct nfs_client *clp)
> +{
> +	struct nfs_server *server;
> +	rcu_read_lock();
> +	list_for_each_entry_rcu(server, &clp->cl_superblocks, client_link) {
> +		if (!(server->flags & NFS_MOUNT_SHUTDOWN)) {
> +			rcu_read_unlock();
> +			return;
> +		}
> +	}
> +	rcu_read_unlock();
> +	nfs_mark_client_ready(clp, -EIO);
> +	shutdown_client(clp->cl_rpcclient);
> +}
> +

Isn't the upshot of this that a mount won't actually get shutdown until
you shutdown all of the mounts to the same server? Personally, I find
that acceptable, but we should note that it is a change in behavior.


>  static ssize_t
>  shutdown_show(struct kobject *kobj, struct kobj_attribute *attr,
>  				char *buf)
> @@ -259,7 +279,6 @@ shutdown_store(struct kobject *kobj, struct kobj_attribute *attr,
>  
>  	server->flags |= NFS_MOUNT_SHUTDOWN;
>  	shutdown_client(server->client);
> -	shutdown_client(server->nfs_client->cl_rpcclient);
>  
>  	if (!IS_ERR(server->client_acl))
>  		shutdown_client(server->client_acl);
> @@ -267,6 +286,7 @@ shutdown_store(struct kobject *kobj, struct kobj_attribute *attr,
>  	if (server->nlm_host)
>  		shutdown_client(server->nlm_host->h_rpcclnt);
>  out:
> +	shutdown_nfs_client(server->nfs_client);
>  	return count;
>  }
>  

-- 
Jeff Layton <jlayton@kernel.org>

  reply	other threads:[~2025-03-26  0:15 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 [this message]
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
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=ecccbc8fca9b057d018bb68acedfb47a6cf76550.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.