From: "J. Bruce Fields" <bfields@fieldses.org>
To: Trond Myklebust <trond@netapp.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH] nfs: remove BKL from callback server
Date: Sun, 29 Nov 2009 16:24:44 -0500 [thread overview]
Message-ID: <20091129212444.GC7216@fieldses.org> (raw)
In-Reply-To: <20091009151151.GB9436@fieldses.org>
By the way, did this get applied?
And is there someplace I should be looking for your pending patches
other than
git://git.linux-nfs.org/projects/trondmy/nfs-2.6.git
? Currently they don't seem to have anything not upstream. (But I may
have overlooked something.)
--b.
On Fri, Oct 09, 2009 at 11:11:51AM -0400, J. Bruce Fields wrote:
> From: J. Bruce Fields <bfields@citi.umich.edu>
>
> The rpc server does not require that service threads take the BKL.
>
> Signed-off-by: J. Bruce Fields <bfields@citi.umich.edu>
> ---
> fs/nfs/callback.c | 12 ------------
> 1 files changed, 0 insertions(+), 12 deletions(-)
>
> Just noticed this while looking for something else.
>
> If these BKL's were cut-and-pasted from lockd or older nfsd code under
> the assumption that the generic rpc server code needed them: that
> assumption was incorrect, and we should apply this patch.
>
> (If there was some nfs-client-specific issue here, then ignore this
> patch.)
>
> diff --git a/fs/nfs/callback.c b/fs/nfs/callback.c
> index 293fa05..e66ec5d 100644
> --- a/fs/nfs/callback.c
> +++ b/fs/nfs/callback.c
> @@ -78,11 +78,6 @@ nfs4_callback_svc(void *vrqstp)
>
> set_freezable();
>
> - /*
> - * FIXME: do we really need to run this under the BKL? If so, please
> - * add a comment about what it's intended to protect.
> - */
> - lock_kernel();
> while (!kthread_should_stop()) {
> /*
> * Listen for a request on the socket
> @@ -104,7 +99,6 @@ nfs4_callback_svc(void *vrqstp)
> preverr = err;
> svc_process(rqstp);
> }
> - unlock_kernel();
> return 0;
> }
>
> @@ -160,11 +154,6 @@ nfs41_callback_svc(void *vrqstp)
>
> set_freezable();
>
> - /*
> - * FIXME: do we really need to run this under the BKL? If so, please
> - * add a comment about what it's intended to protect.
> - */
> - lock_kernel();
> while (!kthread_should_stop()) {
> prepare_to_wait(&serv->sv_cb_waitq, &wq, TASK_INTERRUPTIBLE);
> spin_lock_bh(&serv->sv_cb_lock);
> @@ -183,7 +172,6 @@ nfs41_callback_svc(void *vrqstp)
> }
> finish_wait(&serv->sv_cb_waitq, &wq);
> }
> - unlock_kernel();
> return 0;
> }
>
> --
> 1.6.0.4
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-11-29 21:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-09 15:11 [PATCH] nfs: remove BKL from callback server J. Bruce Fields
2009-11-29 21:24 ` J. Bruce Fields [this message]
2009-11-30 13:44 ` 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=20091129212444.GC7216@fieldses.org \
--to=bfields@fieldses.org \
--cc=linux-nfs@vger.kernel.org \
--cc=trond@netapp.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