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

• To: linux-kernel <[email protected]>
• Subject: question about nfs_execute_read: why do we need to do lock_kernel?
• From: "Xin Zhao" <[email protected]>
• Date: Tue, 25 Apr 2006 00:57:45 -0400
• Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=qL954pAGMDrSg9H+Rh5X99HREmBmikDUl9amH2+hbHPz1jVqMDME+n615a2rJselBDusqjyiFpRX+EwauwG8CYqec9kVCvKmlBdO8l3nBBSpRRFXwDqoZi3SRLl08gcKkQ8ceB2ZbG2Wmd5BPGebN1awYVHosxWs1sJ4FfSxIp4=
• Sender: [email protected]

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()?

Thanks in advance for your help!

xin
-
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: Trond Myklebust <[email protected]>

• Prev by Date: Re: [patch 2/4] kref debugging config option
• Next by Date: Re: question about nfs_execute_read: why do we need to do lock_kernel?
• Previous by thread: [patch 1/2] radix-tree: direct data
• 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]