diff options
author | Jeff Layton <jlayton@primarydata.com> | 2014-07-29 21:34:40 -0400 |
---|---|---|
committer | J. Bruce Fields <bfields@redhat.com> | 2014-07-31 14:20:29 -0400 |
commit | fc5a96c3b70d00c863f69ff4ea7f5dfddbcbc0d8 (patch) | |
tree | 8fe86bd3204e6476928e171530c777a32d6e58ba /firmware/keyspan_pda/xircom_pgs.HEX | |
parent | 3c1c995cc2e49f6f7504586ad07c5d80c6aa3301 (diff) |
nfsd: close potential race in nfsd4_free_stateid
Once we remove the client_mutex, it'll be possible for the sc_type of a
lock stateid to change after it's found and checked, but before we can
go to destroy it. If that happens, we can end up putting the persistent
reference to the stateid more than once, and unhash it more than once.
Fix this by unhashing the lock stateid prior to dropping the cl_lock but
after finding it.
Signed-off-by: Jeff Layton <jlayton@primarydata.com>
Signed-off-by: J. Bruce Fields <bfields@redhat.com>
Diffstat (limited to 'firmware/keyspan_pda/xircom_pgs.HEX')
0 files changed, 0 insertions, 0 deletions