(c) submits an interrupt urb. This urb will not complete
for a long time. The urb is in the async pending list.
(d) releases the interface (as a side effect, this means
that driver_disconnect will NOT be called on hub removal).
Note that the urb is still in the async pending list.
Which would be the problem. If usbfs had unlinked it, the
oops would vanish -- yes? Good find!
I think it's a driver bug (usbfs) that it released any
interface with an urb still pending.
I agree that it'd be better if usbcore guarded against the
inevitable driver bugs, but that seems like 2.5 material
due to the kind of changes needed.- 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
