Re: Debugging scsi abort handling ?

[Paolo Bonzini <pbonzini@redhat.com>]

Il 25/08/2014 12:28, Bart Van Assche ha scritto:
> 
> From SPC-4: "7.5.8 Control mode page [ ... ] A task aborted status (TAS)
> bit set to zero specifies that aborted commands shall be terminated by
> the device server without any response to the application client. A TAS
> bit set to one specifies that commands aborted by the actions of an I_T
> nexus other than the I_T nexus on which the command was received shall
> be completed with TASK ABORTED status (see SAM-5)."

Note the "aborted by the actions of an I_T nexus other than the I_T
nexus on which the command was received".

In practice, this means that TASK ABORTED should only happen if you use
the CLEAR TASK SET tmf and TST is not set to 001b (i.e. _not_ to "per
I_T nexus") in the Control mode page.  It should never happen for a pen
drive.

Setting TASK ABORTED aside, the important part is that an abort can do
one of two things:

- complete the command, and then eh_abort should return after the driver
has noticed the completion and called the ->scsi_done callback for the
Scsi_Cmnd*.

- abort the command, and then the driver should never call the
->scsi_done callback for the Scsi_Cmnd*.

Paolo