Hi, On 08/25/2014 01:15 PM, Paolo Bonzini wrote: > 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*. Thanks Bart and Paolo, your insights into this are greatly appreciated. So with uas there are separate usb transaction for cmd, data in, data out and sense for each tag. At the time of abort, usually one of data in / data out and a sense usb transaction will be outstanding. There already is logic in the driver to kill the data in / out transactions if a sense gets returned (usually with an error) before they are done. So if I'm reading this correctly, then on a successful abort, the sense transaction (if not already completed by the target) should be cancelled as it will never complete, correct ? I wish the uas spec contained some more details on this, but it is very vague wrt task management (well it is vague in general, task management just is extra hard to test). Regards, Hans -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
