On 08/08/05 16:41, Alan Stern wrote: > I still have one related question. This is a little bit off to one > side, but maybe you folks can suggest possible solutions. The question > concerns a deadlock I _was_ able to generate earlier today with a patched > usb-storage. > > My USB mass-storage test device doesn't respond to TEST UNIT READY, so it > causes a timeout and kicks the error handler into action. This happens > during device scanning, just prior to reading the partition table. The > error handler goes through various stages of processing, leading up to a > bus reset. I disconnected the USB device just before the bus reset > routine was called. I think that "scanning" is a special process which should involve the minimum of error handling, by either ignoring errors and trying to connect to the device anyway, or on the first error, give up the device. Which policy would one follow depends on the transport. If the latter, you need to blacklist the device as not supporting TUR. Then on any error, like you pulling the cable during scanning, the scanning process will give up and all will be well. Luben - : send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
