diff options
| author | Trond Myklebust <Trond.Myklebust@netapp.com> | 2008-12-23 15:21:31 -0500 |
|---|---|---|
| committer | Trond Myklebust <Trond.Myklebust@netapp.com> | 2008-12-23 15:21:31 -0500 |
| commit | 88a9fe8cae3bb52e82489447f45e8d7ba1409ca8 (patch) | |
| tree | acef9d0b7d4c8c2e98faf852ab8bc0173842fbe5 /security | |
| parent | 136221fc3219b3805c48db5da065e8e3467175d4 (diff) | |
| download | kernel_samsung_espresso10-88a9fe8cae3bb52e82489447f45e8d7ba1409ca8.zip kernel_samsung_espresso10-88a9fe8cae3bb52e82489447f45e8d7ba1409ca8.tar.gz kernel_samsung_espresso10-88a9fe8cae3bb52e82489447f45e8d7ba1409ca8.tar.bz2 | |
SUNRPC: Remove the last remnant of the BKL...
Somehow, this escaped the previous purge. There should be no need to keep
any extra locks in the XDR callbacks.
The NFS client XDR code only writes into private objects, whereas all reads
of shared objects are confined to fields that do not change, such as
filehandles...
Ditto for lockd, the NFSv2/v3 client mount code, and rpcbind.
The nfsd XDR code may require the BKL, but since it does a synchronous RPC
call from a thread that already holds the lock, that issue is moot.
Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
Diffstat (limited to 'security')
0 files changed, 0 insertions, 0 deletions