>>> 1) If command_abort() is called by scsi subsytem, process deadlocks 
>>> on wait_for_completion(&(us->notify))
>>
>> For this one, it'd be good to know if 2.5.latest does the same thing.
> 
> 2.5.38 oopses on the last line if usb_stor_abort_transport (us->srb == 
> NULL). I attepted to fix it:

Looks to me like you certainly did find some kind of usb-storage problems,
regardless of what else is going on.  Fault handling shouldn't trigger
oopses or hangs, any more than any other code.  Matt?

Although I wonder if there's something else going on first.  Your device
seems to not like the INQUIRY command; perhaps the storage driver should
be told some quirks about your particular adapter.

- Dave




-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel

Reply via email to