On Fri, Feb 12, 2010 at 11:30 PM, Joe Eykholt <[email protected]> wrote:
>
> [ ... ]
>
> Another issue there is that it calls scst_unregister_session() right
> away so there could be commands still using the session at that point.
> I have a note to do it later when I'm sure there are no more
> commands in progress.

scst_unregister_session() aborts all outstanding commands and waits
with the last step of session unregistration until the target driver
has called scst_tgt_cmd_done() for each command associated with that
session. It is not necessary in a target driver to keep track of which
SCST commands are associated with which session.

Bart.
_______________________________________________
devel mailing list
[email protected]
http://www.open-fcoe.org/mailman/listinfo/devel

Reply via email to