From: "J. Bruce Fields" <bfields@fieldses.org>
To: Stanislav Kinsbursky <skinsbursky@parallels.com>
Cc: linux-nfs@vger.kernel.org, Trond.Myklebust@netapp.com,
linux-kernel@vger.kernel.org, devel@openvz.org
Subject: Re: [PATCH] nfsd4: remove state lock from nfs4_state_shutdown
Date: Tue, 27 Nov 2012 17:11:05 -0500 [thread overview]
Message-ID: <20121127221105.GJ27142@fieldses.org> (raw)
In-Reply-To: <20121121150730.6644.99859.stgit@localhost.localdomain>
OK, applying.--b.
On Wed, Nov 21, 2012 at 06:07:38PM +0300, Stanislav Kinsbursky wrote:
> Protection of __nfs4_state_shutdown() with nfs4_lock_state() looks redundant.
>
> This function is called by the last NFSd thread on it's exit and state lock
> protects actually two functions (del_recall_lru is protected by recall_lock):
> 1) nfsd4_client_tracking_exit
> 2) __nfs4_state_shutdown_net
>
> "nfsd4_client_tracking_exit" doesn't require state lock protection, because it's
> state can be modified only by tracker callbacks.
> Here a re they:
> 1) create: is called only from nfsd4_proc_compound.
> 2) remove: is called from either nfsd4_proc_compound or nfs4_laundromat.
> 3) check: is called only from nfsd4_proc_compound.
> 4) grace_done; called only from nfs4_laundromat.
>
> nfsd4_proc_compound is called onll by NFSd kthread, which is exiting right
> now.
> nfs4_laundromat is called by laundry_wq. But laundromat_work was canceled
> already.
>
> "__nfs4_state_shutdown_net" also doesn't require state lock protection,
> because all NFSd kthreads are dead, and no race can happen with NFSd start,
> because "nfsd_up" flag is still set.
> Moreover, all Nfsd shutdown is protected with global nfsd_mutex.
>
> Signed-off-by: Stanislav Kinsbursky <skinsbursky@parallels.com>
> ---
> fs/nfsd/nfs4state.c | 2 --
> 1 files changed, 0 insertions(+), 2 deletions(-)
>
> diff --git a/fs/nfsd/nfs4state.c b/fs/nfsd/nfs4state.c
> index e75872f..d41cc71 100644
> --- a/fs/nfsd/nfs4state.c
> +++ b/fs/nfsd/nfs4state.c
> @@ -4926,9 +4926,7 @@ nfs4_state_shutdown(void)
> cancel_delayed_work_sync(&nn->laundromat_work);
> destroy_workqueue(laundry_wq);
> locks_end_grace(&nn->nfsd4_manager);
> - nfs4_lock_state();
> __nfs4_state_shutdown(net);
> - nfs4_unlock_state();
> nfsd4_destroy_callback_queue();
> }
>
>
prev parent reply other threads:[~2012-11-27 22:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-21 15:07 [PATCH] nfsd4: remove state lock from nfs4_state_shutdown Stanislav Kinsbursky
2012-11-27 22:11 ` J. Bruce Fields [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=20121127221105.GJ27142@fieldses.org \
--to=bfields@fieldses.org \
--cc=Trond.Myklebust@netapp.com \
--cc=devel@openvz.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=skinsbursky@parallels.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).