----- Original Message -----
From: Matthew Dharm <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, May 11, 2000 2:53 AM
Subject: eh_abort_handler() behavior?
> What is the proper behavior for a host driver when the eh_abort_handler()
> is called? Specifically, what happens to the commands in the command
queue
> and the command being worked on?
I would have to go back to the SCSI standards to see exactly what is
supposed to happen. There is a specific section that covers the actions of
each one of the entrypoints.
WRT the abort entrypoint, I *believe* (I am doing this from memory),
that commands in the queue are left alone - it is only the one specific
command that is being aborted. The idea is that if the return code
indicates success, then both the device and the host driver should have
flushed the command from the set of pending operations. The mid-level
assumes that once an abort has succeeded that everything should be back to a
normal state, and that the host and device are ready to accept new commands
(it tries a couple, just to make sure), but that is the assumption.
-Eric
-
To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
the body of a message to [EMAIL PROTECTED]
