public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* SCSI reusing tags during error recovery
@ 2011-01-10 18:21 Luben Tuikov
  0 siblings, 0 replies; only message in thread
From: Luben Tuikov @ 2011-01-10 18:21 UTC (permalink / raw)
  To: linux-scsi, linux-kernel, James Bottomley

Observed is on the wire, the following scenario:

0: Tag A (READ) -->
  (Times out)
1: Tag X (TMF ABORT TASK, TTBM=A) -->
2: Tag X (TMR FUNCTION COMPLETE) <--
3: Tag A (TUR) -->
4: Tag A (TUR status GOOD) <--
5: Tag A+2 (some command) -->
...

Undoubtedly resulting from the SCSI layer reusing the request
structure of the timed out Tag A to issue the Test Unit Ready
command, sequence 3.

However, if the task manager were unable to abort Tag A and
returned a different task management result, then the TUR would
complete with CHECK CONDITION (ABORTED COMMAND, OVERLAPPED
COMMANDS ATTEMPTED). Not all transports require the task router
to implement overlapped tag checking, and in most it is optional.
The TUR should go out with Tag A+1.

The SCSI layer should ideally, not perform error recovery ("error
handling" to use Linux' own terminology) on behalf of a timed out
request, but allow higher layers to issue TMF only based on a
ITLQ (tag, a number) or ITL (LUN, a structure) or IT nexus
(target port).

A previous issue I raised, tag generation for tags of task
management functions, can be found here:
http://marc.info/?l=linux-scsi&m=128902337522890&w=2

   Luben


^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2011-01-10 18:21 UTC | newest]

Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-01-10 18:21 SCSI reusing tags during error recovery Luben Tuikov

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox