Re: question about nfs_execute_read: why do we need to do lock_kernel?

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

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: question about nfs_execute_read: why do we need to do lock_kernel?
    • From: "Xin Zhao" <[email protected]>

• References:
  • question about nfs_execute_read: why do we need to do lock_kernel?
    • From: "Xin Zhao" <[email protected]>

• Prev by Date: question about nfs_execute_read: why do we need to do lock_kernel?
• Next by Date: Re: [patch 1/2] raid6_end_write_request() spinlock fix
• Previous by thread: question about nfs_execute_read: why do we need to do lock_kernel?
• Next by thread: Re: question about nfs_execute_read: why do we need to do lock_kernel?
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]