From: Jeff Layton <jlayton@kernel.org>
To: Christoph Hellwig <hch@lst.de>, brauner@kernel.org
Cc: trond.myklebust@hammerspace.com, anna@kernel.org, jack@suse.cz,
linux-nfs@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] NFS: switch back to using kill_anon_super
Date: Thu, 31 Aug 2023 09:29:14 -0400 [thread overview]
Message-ID: <2f121ee5b7fad547ac833a5e0e986866d1177e21.camel@kernel.org> (raw)
In-Reply-To: <20230831052940.256193-1-hch@lst.de>
On Thu, 2023-08-31 at 07:29 +0200, Christoph Hellwig wrote:
> NFS switch to open coding kill_anon_super in 7b14a213890a
> ("nfs: don't call bdi_unregister") to avoid the extra bdi_unregister
> call. At that point bdi_destroy was called in nfs_free_server and
> thus it required a later freeing of the anon dev_t. But since
> 0db10944a76b ("nfs: Convert to separately allocated bdi") the bdi has
> been free implicitly by the sb destruction, so this isn't needed
> anymore.
>
> By not open coding kill_anon_super, nfs now inherits the fix in
> dc3216b14160 ("super: ensure valid info"), and we remove the only
> open coded version of kill_anon_super.
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> ---
> fs/nfs/super.c | 4 +---
> 1 file changed, 1 insertion(+), 3 deletions(-)
>
> diff --git a/fs/nfs/super.c b/fs/nfs/super.c
> index 2284f749d89246..0d6473cb00cb3e 100644
> --- a/fs/nfs/super.c
> +++ b/fs/nfs/super.c
> @@ -1339,15 +1339,13 @@ int nfs_get_tree_common(struct fs_context *fc)
> void nfs_kill_super(struct super_block *s)
> {
> struct nfs_server *server = NFS_SB(s);
> - dev_t dev = s->s_dev;
>
> nfs_sysfs_move_sb_to_server(server);
> - generic_shutdown_super(s);
> + kill_anon_super(s);
>
> nfs_fscache_release_super_cookie(s);
>
> nfs_free_server(server);
> - free_anon_bdev(dev);
> }
> EXPORT_SYMBOL_GPL(nfs_kill_super);
>
Nice. Long overdue. This also might explain why ceph was once this way
before we changed it here:
470a5c77eac0 ceph: use kill_anon_super helper
In any case:
Reviewed-by: Jeff Layton <jlayton@kernel.org>
next prev parent reply other threads:[~2023-08-31 13:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-31 5:29 [PATCH] NFS: switch back to using kill_anon_super Christoph Hellwig
2023-08-31 7:59 ` Christian Brauner
2023-08-31 10:54 ` Jan Kara
2023-08-31 13:29 ` Jeff Layton [this message]
2023-08-31 13:32 ` Christoph Hellwig
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=2f121ee5b7fad547ac833a5e0e986866d1177e21.camel@kernel.org \
--to=jlayton@kernel.org \
--cc=anna@kernel.org \
--cc=brauner@kernel.org \
--cc=hch@lst.de \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=trond.myklebust@hammerspace.com \
/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;
as well as URLs for NNTP newsgroup(s).