From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Xin Zhao <uszhaoxin@gmail.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: question about nfs_execute_read: why do we need to do lock_kernel?
Date: Tue, 25 Apr 2006 01:09:03 -0400 [thread overview]
Message-ID: <1145941743.8164.6.camel@lade.trondhjem.org> (raw)
In-Reply-To: <4ae3c140604242157k26f39f71qcf6eed811f1e2d8@mail.gmail.com>
On Tue, 2006-04-25 at 00:57 -0400, Xin Zhao wrote:
> This question may be dumb. But I am curious why in nfs_execute_read()
> function, rpc_execute is bracketed with lock_kernel() and
> unlock_kernel()?
We're keeping the BKL for the moment simply because we are not done
auditing all the RPC code for potential races. When that is done, we
will be able to remove it.
Cheers,
Trond
next prev parent reply other threads:[~2006-04-25 5:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-25 4:57 Xin Zhao
2006-04-25 5:09 ` Trond Myklebust [this message]
2006-04-25 14:08 ` Xin Zhao
2006-04-25 14:26 ` Trond Myklebust
2006-04-25 14:37 ` Peter Staubach
2006-04-25 15:31 ` Xin Zhao
2006-04-25 15:57 ` 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=1145941743.8164.6.camel@lade.trondhjem.org \
--to=trond.myklebust@fys.uio.no \
--cc=linux-kernel@vger.kernel.org \
--cc=uszhaoxin@gmail.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
all inboxes | Powered by JetHome®