Windows: cm_Analyze retries vs CM_REQ_NORETRY
authorJeffrey Altman <jaltman@your-file-system.com>
Mon, 18 Nov 2013 04:03:43 +0000 (23:03 -0500)
committerJeffrey Altman <jaltman@your-file-system.com>
Wed, 20 Nov 2013 23:31:46 +0000 (15:31 -0800)
commita1b5a1d42280753de13094006dcc130fede978a1
treefe61722cfc549b18d3f44744856f9543f9780ac5
parenta95b1f2f15d3f8efff74ad7df5085b8f30885dbc
Windows: cm_Analyze retries vs CM_REQ_NORETRY

CM_REQ_NORETRY is set by threads that want all errors returned
immediately.  However, there are some errors that should never
be returned:

  RX_MSGSIZE
  RX_CALL_BUSY
  VNOSERVICE
  RX_CALL_IDLE
  RXKADEXPIRED
  VICECONNBAD
  VICETOKENDEAD

For these errors even if the thread has requested no retries a RPC
retry must be performed.

Change-Id: I692f65a9fdbbf27fc880ac8912fc72c1d1357c6d
Reviewed-on: http://gerrit.openafs.org/10470
Tested-by: BuildBot <buildbot@rampaginggeek.com>
Reviewed-by: Jeffrey Altman <jaltman@your-file-system.com>
src/WINNT/afsd/cm_conn.c