James Bottomley [EMAIL PROTECTED] wrote: > On Wed, 2004-09-29 at 16:31, Mike Anderson wrote: > > James Bottomley [EMAIL PROTECTED] wrote: > > > Once you've called scsi_remove_host() the mid-layer will take control of > > > your in-flight commands (if there are any) and error them back to the > > > user. You need to take any actions to clean up internal structures > > > belonging to the commands *before* you do a scsi_remove_host. > > > > > > > How do we address the problem we get into with the reordering in > > scsi_remove_host (i.e. the call to scsi_forget_host prior to > > scsi_host_cancel) if we possibly generate new io from sd_sync_cache > > that will cause the error handler to fire up if the LLDD just lets the > > command fall on the floor with no response. > > That's why LLD's are responsible for erroring all commands issued at > this time if the removal is a surprise ejection. The commands have to > be errored in a way (like DID_NO_CONNECT) that won't excite the error > handler. >
ok, thanks for the clarification. Your previous statement seemed to imply once scsi_remove_host was called the LLDD had no responsibility for calling done on commands sent to the LLDDs queuecommand. So now that this thread and the other thread related to similar shutdown issues has grown long is the next step to see if we can get the usb queuecommand to return DID_NO_CONNECT in this shutdown case. -andmike -- Michael Anderson [EMAIL PROTECTED] ------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
