nfsd: Protect adding/removing lock owners using client_lock

Browse source

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>

...

This commit is contained in:

Trond Myklebust 2014-07-29 21:34:35 -04:00 • committed by J. Bruce Fields

parent 7ffb588086

commit c58c6610ec

1 changed files with 61 additions and 8 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

69

fs/nfsd/nfs4state.c

View file