Task management questions

[Gwendal Grignou <ggrignou@silverbacksystems.com>]

I have a question about the section 3.5.1 page 69.
The paragrah starting with "ABORT TASK MUST",the last sentene says "The task 
management response MUST be issued after the command status (if any) was 
issued." : it means the initiator will receive, on the same connection, a 
status for the aborted task and AFTER, a response for the task management 
function. 

In the paragraph before (starting with "For all these functions,",), it is 
specified that the target should send a status for all aborted tasks, but the 
task management response can happen at any time after the task management 
request has been received by the target "The task management response MAY be 
issued by the target immediately after marking all tasks to be aborted."

Why such a difference between "ABORT TASK" function and other functions ?

About, "LOGICAL UNIT RESET", it is stated "the target MUST behave as dictated 
by the Logical Unit Reset function in [SAM2]." However, in SAM2, taks should 
be aborted as described in section 5.6 of SAM2, which says , in section 
5.6.2, about initiator aborting their own task "When an initiator causes its 
own task(s) to be aborted, no notification that the task(s) have been aborted 
shall be returned to the initiator other than the completion response for the 
command or task management function action that caused the task(s) to be 
aborted and notification(s) associated with related effects of the action 
(e.g., a target reset unit attention condition)." Does it means the iSCSI 
target may not send a status for the aborted tasks in case of a 
"LOGICAL UNIT RESET" ? (and subsequently for TARGET RESET [WARM or COLD] 
which triggers LOGICAL UNIT RESET for each LUs [SAM2, section 5.8.6]). It 
does not match with the requirement in the paragraph concerning all the task 
management functions in general.

Can you elaborate more on those requirements ?

Thanks a lot,

Gwendal.