summaryrefslogtreecommitdiffstats
path: root/crypto
diff options
context:
space:
mode:
authorTrond Myklebust <Trond.Myklebust@netapp.com>2008-12-23 15:21:45 -0500
committerTrond Myklebust <Trond.Myklebust@netapp.com>2008-12-23 15:21:45 -0500
commit95d35cb4c473c754824967c0b069bbeb7efa4847 (patch)
treebd46a5b0e4d35f9256cf44ca2706493fc3dd2819 /crypto
parent19e03c570e6099ffaf24e5628d4fe1a8acbe820d (diff)
downloadlinux-stable-95d35cb4c473c754824967c0b069bbeb7efa4847.tar.gz
linux-stable-95d35cb4c473c754824967c0b069bbeb7efa4847.tar.bz2
linux-stable-95d35cb4c473c754824967c0b069bbeb7efa4847.zip
NFSv4: Remove nfs_client->cl_sem
Now that we're using the flags to indicate state that needs to be recovered, as well as having implemented proper refcounting and spinlocking on the state and open_owners, we can get rid of nfs_client->cl_sem. The only remaining case that was dubious was the file locking, and that case is now covered by the nfsi->rwsem. Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
Diffstat (limited to 'crypto')
0 files changed, 0 insertions, 0 deletions