nfsd: Add a mutex to protect the NFSv4.0 open owner replay cache
We don't want to rely on the client_mutex for protection in the case of NFSv4 open owners. Instead, we add a mutex that will only be taken for NFSv4.0 state mutating operations, and that will be released once the entire compound is done. Also, ensure that nfsd4_cstate_assign_replay/nfsd4_cstate_clear_replay take a reference to the stateowner when they are using it for NFSv4.0 open and lock replay caching. Signed-off-by: Trond Myklebust <trond.myklebust@primarydata.com> Signed-off-by: Jeff Layton <jlayton@primarydata.com> Signed-off-by: J. Bruce Fields <bfields@redhat.com>
This commit is contained in:

committed by
J. Bruce Fields

parent
6b180f0b57
commit
58fb12e6a4
@@ -3925,8 +3925,6 @@ status:
|
||||
*
|
||||
* XDR note: do not encode rp->rp_buflen: the buffer contains the
|
||||
* previously sent already encoded operation.
|
||||
*
|
||||
* called with nfs4_lock_state() held
|
||||
*/
|
||||
void
|
||||
nfsd4_encode_replay(struct xdr_stream *xdr, struct nfsd4_op *op)
|
||||
|
Reference in New Issue
Block a user