Linux NFS development
 help / color / mirror / Atom feed
From: Jeff Layton <jlayton@kernel.org>
To: Chuck Lever III <chuck.lever@oracle.com>
Cc: Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
	JianHong Yin <jiyin@redhat.com>
Subject: Re: [PATCH] nfsd: don't destroy global nfs4_file table in per-net shutdown
Date: Sat, 11 Feb 2023 15:47:43 -0500	[thread overview]
Message-ID: <11ac2dd02431095cb861bc4ea1ad7529fc79d3c5.camel@kernel.org> (raw)
In-Reply-To: <03EDD716-A995-49A4-B9AF-E1AA13AAD16E@oracle.com>

On Sat, 2023-02-11 at 20:31 +0000, Chuck Lever III wrote:
> 
> > On Feb 11, 2023, at 7:50 AM, Jeff Layton <jlayton@kernel.org> wrote:
> > 
> > The nfs4_file table is global, so shutting it down when a containerized
> > nfsd is shut down is wrong and can lead to double-frees. Tear down the
> > nfs4_file_rhltable in nfs4_state_shutdown instead of
> > nfs4_state_shutdown_net.
> 
> D'oh!
> 
> 
> > Fixes: d47b295e8d76 (NFSD: Use rhashtable for managing nfs4_file objects)
> > Link: https://bugzilla.redhat.com/show_bug.cgi?id=2169017
> > Reported-by: JianHong Yin <jiyin@redhat.com>
> > Signed-off-by: Jeff Layton <jlayton@kernel.org>
> 
> Thanks to you and JianHong. Applied to nfsd-fixes.
> 

Thanks for grabbing it quickly. It'd be great to get this in before v6.2
ships...

> 
> > ---
> > fs/nfsd/nfs4state.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> > 
> > diff --git a/fs/nfsd/nfs4state.c b/fs/nfsd/nfs4state.c
> > index af22dfdc6fcc..a202be19f26f 100644
> > --- a/fs/nfsd/nfs4state.c
> > +++ b/fs/nfsd/nfs4state.c
> > @@ -8218,7 +8218,6 @@ nfs4_state_shutdown_net(struct net *net)
> > 
> > 	nfsd4_client_tracking_exit(net);
> > 	nfs4_state_destroy_net(net);
> > -	rhltable_destroy(&nfs4_file_rhltable);
> > #ifdef CONFIG_NFSD_V4_2_INTER_SSC
> > 	nfsd4_ssc_shutdown_umount(nn);
> > #endif
> > @@ -8228,6 +8227,7 @@ void
> > nfs4_state_shutdown(void)
> > {
> > 	nfsd4_destroy_callback_queue();
> > +	rhltable_destroy(&nfs4_file_rhltable);
> > }
> > 
> > static void
> > -- 
> > 2.39.1
> > 
> 
> --
> Chuck Lever
> 
> 
> 

-- 
Jeff Layton <jlayton@kernel.org>

      reply	other threads:[~2023-02-11 20:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-11 12:50 [PATCH] nfsd: don't destroy global nfs4_file table in per-net shutdown Jeff Layton
2023-02-11 20:31 ` Chuck Lever III
2023-02-11 20:47   ` 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=11ac2dd02431095cb861bc4ea1ad7529fc79d3c5.camel@kernel.org \
    --to=jlayton@kernel.org \
    --cc=chuck.lever@oracle.com \
    --cc=jiyin@redhat.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