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
@@ -469,12 +469,9 @@ out:
|
||||
fh_put(resfh);
|
||||
kfree(resfh);
|
||||
}
|
||||
nfsd4_cleanup_open_state(open, status);
|
||||
if (open->op_openowner && !nfsd4_has_session(cstate))
|
||||
cstate->replay_owner = &open->op_openowner->oo_owner;
|
||||
nfsd4_cleanup_open_state(cstate, open, status);
|
||||
nfsd4_bump_seqid(cstate, status);
|
||||
if (!cstate->replay_owner)
|
||||
nfs4_unlock_state();
|
||||
nfs4_unlock_state();
|
||||
return status;
|
||||
}
|
||||
|
||||
@@ -1395,10 +1392,7 @@ encode_op:
|
||||
args->ops, args->opcnt, resp->opcnt, op->opnum,
|
||||
be32_to_cpu(status));
|
||||
|
||||
if (cstate->replay_owner) {
|
||||
nfs4_unlock_state();
|
||||
cstate->replay_owner = NULL;
|
||||
}
|
||||
nfsd4_cstate_clear_replay(cstate);
|
||||
/* XXX Ugh, we need to get rid of this kind of special case: */
|
||||
if (op->opnum == OP_READ && op->u.read.rd_filp)
|
||||
fput(op->u.read.rd_filp);
|
||||
|
Reference in New Issue
Block a user