nfsd: Protect adding/removing lock owners using client_lock
authorTrond Myklebust <trond.myklebust@primarydata.com>
Wed, 30 Jul 2014 01:34:35 +0000 (21:34 -0400)
committerJ. Bruce Fields <bfields@redhat.com>
Thu, 31 Jul 2014 18:20:25 +0000 (14:20 -0400)
commitc58c6610ec248134b0b0ede2ac80859bf1cefa29
tree5a5aeadaf6abd7ffd45bcf5e17ef4448db06b47d
parent7ffb588086e941aa0a46a33e2bf2bf3c0963ed98
nfsd: Protect adding/removing lock owners using client_lock

Once we remove client mutex protection, we'll need to ensure that
stateowner lookup and creation are atomic between concurrent compounds.
Ensure that alloc_init_lock_stateowner checks the hashtable under the
client_lock before adding a new element.

Signed-off-by: Trond Myklebust <trond.myklebust@primarydata.com>
Signed-off-by: J. Bruce Fields <bfields@redhat.com>
fs/nfsd/nfs4state.c