NFSv4.1: Don't update sequence number if rpc_task is not sent
If we fail to contact the gss upcall program, then no message will be sent to the server. The client still updated the sequence number, however, and this lead to NFS4ERR_SEQ_MISMATCH for the next several RPC calls. Signed-off-by: Bryan Schumaker <bjschuma@netapp.com> Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
This commit is contained in:

committed by
Trond Myklebust

parent
47c2199b6e
commit
468f86134e
@@ -444,8 +444,8 @@ static int nfs41_sequence_done(struct rpc_task *task, struct nfs4_sequence_res *
|
||||
if (res->sr_status == 1)
|
||||
res->sr_status = NFS_OK;
|
||||
|
||||
/* -ERESTARTSYS can result in skipping nfs41_sequence_setup */
|
||||
if (!res->sr_slot)
|
||||
/* don't increment the sequence number if the task wasn't sent */
|
||||
if (!RPC_WAS_SENT(task))
|
||||
goto out;
|
||||
|
||||
/* Check the SEQUENCE operation status */
|
||||
|
Reference in New Issue
Block a user