From: Jeff Layton <jlayton@kernel.org>
To: Trond Myklebust <trondmy@kernel.org>, Anna Schumaker <anna@kernel.org>
Cc: linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org,
Eric Dumazet <edumazet@google.com>
Subject: Re: [PATCH] nfs: add a refcount tracker for struct net as held by the nfs_client
Date: Tue, 25 Mar 2025 09:16:43 -0400 [thread overview]
Message-ID: <b777dcb43f68497d53bfc1038dfa01e29122d32a.camel@kernel.org> (raw)
In-Reply-To: <20250325-nfs-net-nef-v1-1-0142cbd7e9ea@kernel.org>
On Tue, 2025-03-25 at 07:44 -0400, Jeff Layton wrote:
> Eric added refcount trackers to several long-held netns references in
> the sunrpc layer in 2022. Add a tracker to the netns reference held by
> the nfs_client as well.
>
> Cc: Eric Dumazet <edumazet@google.com>
> Signed-off-by: Jeff Layton <jlayton@kernel.org>
> ---
> fs/nfs/client.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/fs/nfs/client.c b/fs/nfs/client.c
> index 3b0918ade53cd331d76baaa86fd2adec5d945b78..2ce58f2d6bf50924c38962ddedb7f0ca68752a8a 100644
> --- a/fs/nfs/client.c
> +++ b/fs/nfs/client.c
> @@ -180,7 +180,7 @@ struct nfs_client *nfs_alloc_client(const struct nfs_client_initdata *cl_init)
> clp->cl_proto = cl_init->proto;
> clp->cl_nconnect = cl_init->nconnect;
> clp->cl_max_connect = cl_init->max_connect ? cl_init->max_connect : 1;
> - clp->cl_net = get_net(cl_init->net);
> + clp->cl_net = get_net_track(cl_init->net, &clp->cl_ns_tracker, GFP_KERNEL);
>
> #if IS_ENABLED(CONFIG_NFS_LOCALIO)
> seqlock_init(&clp->cl_boot_lock);
> @@ -250,7 +250,7 @@ void nfs_free_client(struct nfs_client *clp)
> if (!IS_ERR(clp->cl_rpcclient))
> rpc_shutdown_client(clp->cl_rpcclient);
>
> - put_net(clp->cl_net);
> + put_net_track(clp->cl_net, &clp->cl_ns_track);
> put_nfs_version(clp->cl_nfs_mod);
> kfree(clp->cl_hostname);
> kfree(clp->cl_acceptor);
>
> ---
> base-commit: 38fec10eb60d687e30c8c6b5420d86e8149f7557
> change-id: 20250325-nfs-net-nef-fc2709b4efda
>
> Best regards,
Please disregard this patch. This is an earlier version of the one I
_actually_ tested. I'll send a v2 when I get back from LSF.
--
Jeff Layton <jlayton@kernel.org>
prev parent reply other threads:[~2025-03-25 13:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-25 11:44 [PATCH] nfs: add a refcount tracker for struct net as held by the nfs_client Jeff Layton
2025-03-25 13:16 ` Jeff Layton [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=b777dcb43f68497d53bfc1038dfa01e29122d32a.camel@kernel.org \
--to=jlayton@kernel.org \
--cc=anna@kernel.org \
--cc=edumazet@google.com \
--cc=linux-kernel@vger.kernel.org \
--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