Windows: cm_Analyze retries vs CM_REQ_NORETRY (2)

Commit a1b5a1d422 left out a critical
part of the patch.  The check for "retry < 2" when determining whether
retries should be skipped due to CM_REQ_NORETRY.

Change-Id: I9b750e2bab11d28813447b2ee92287b8dcfbbba3
Reviewed-on: http://gerrit.openafs.org/11131
Tested-by: BuildBot <buildbot@rampaginggeek.com>
Reviewed-by: Jeffrey Altman <jaltman@your-file-system.com>
This commit is contained in:
Jeffrey Altman 2014-05-08 09:06:07 -04:00
parent a111d0db77
commit aad509a7e1

View File

@ -1378,7 +1378,7 @@ cm_Analyze(cm_conn_t *connp,
/* If not allowed to retry, don't */
if (dead_session ||
!forcing_new && (reqp->flags & CM_REQ_NORETRY) &&
!forcing_new && (retry < 2) && (reqp->flags & CM_REQ_NORETRY) &&
!(errorCode > -64 && errorCode <= RX_INVALID_OPERATION))
retry = 0;