RE: iSCSI: aborting an immediate command with ABORT TASK

[Paul Koning <ni1d@arrl.net>]

>>>>> "Julian" == Julian Satran <Julian_Satran@il.ibm.com> writes:

 Julian> The next command can't be clobered. Abort Task acts on
 Julian> command up to 6 (included) but not 7- and it has to be on the
 Julian> same connection as the aborted command. That insures that it
 Julian> will abort the first immediate but not the non-immediate
 Julian> after.

If the abort has to be sent on the same connection as the command
being aborted, then it cannot overtake an immediate command preceding
it.  At least not in the network stack...  So that seems to eliminate
the case that David was worrying about. 

    paul