[Scst-devel] Re: query about scst task mgmt handling

[Vladislav B. <vs...@vl...>]

Krishnanand,

You asked very goog question.

I haven't found anywhere in SAM-2/3 that ABORT TASK shall fail if the
command (task) is being executed (i.e. sent to the mid-leyer). It says,
"...a response of FUNCTION COMPLETE shall indicate that the task was
aborted or was not in the task set". Tasks that being executed are still
in the task set. So, there is not such logic in SCST. For ABORT TASK
handling see scst_abort_cmd().

Anyway, your question inspired me to find some defects in the current tas=
k
management logic. So, thanks

I didn't understand your "PS" question.

Vlad

> I started browsing thru the sources just today....after a quick browse
> thru
> the following thing struck me as ODD:
>
> i see that some lists are being maintained in SCST as cmd_init_list,
> cmd_list and active_cmd_list.
>
> A cmd submitted to the SCSI midlayer is on the active_cmd_list.
>
> When a TASK ABORT comes for a cmd which is already submitted to the
> MidLayer
> then the abort task function should fail since the cmd cant be aborted.
>
> I couldnt locate code which does this...can u give a hint.
>
> PS: Also could u give an example where a non-disk type of SCSI device
> would
> support TM functionality (I'm a SCSI newbie).
>
> cheers,
> tkrishna
>