commit | c58c6610ec248134b0b0ede2ac80859bf1cefa29 | [log] [tgz] |
---|---|---|
author | Trond Myklebust <trond.myklebust@primarydata.com> | Tue Jul 29 21:34:35 2014 -0400 |
committer | J. Bruce Fields <bfields@redhat.com> | Thu Jul 31 14:20:25 2014 -0400 |
tree | 5a5aeadaf6abd7ffd45bcf5e17ef4448db06b47d | |
parent | 7ffb588086e941aa0a46a33e2bf2bf3c0963ed98 [diff] |
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>