Now... wait a second here....
You say the dirver "is supposed to wait until all urbs" are completed...
but we're talking about the case where the device is now gone...
So how do the urbs complete? Something is causing them to complete when
the cable is removed -- that's the behavior I've observed, at least.
Matt
On Thu, Jul 04, 2002 at 01:23:54PM -0700, David Brownell wrote:
> >>Test case: user pulls out the usb cable while a transfer is in progress.
> >>urb submitted to the device, reply not yet received.
> >>Result: storage_disconnect() would hang for 20 seconds until
> >>command_abort() is called.
> >
> >
> > No, not quite. The HCD accelerates the URBs to completion if the device
> > is removed with an URB pending on it. It therefore shouldn't hang for the
> > timeout -- if you're seeing this behavior, then the HCD is broken.
>
> Actually all of the interesting work is triggered by khubd,
> and then the device driver.
>
> Khubd calls usb_disconnect() for the device. That disconnects
> each driver (which is supposed to wait until all urbs it's
> submitted have completed, and not submit any more URBS).
>
> Only at the very end of this does the HCD hear anything about
> devices going away. If there's any URB still submitted at that
> point it's not a bug in the HCD at all ... but in a device
> driver that didn't implement disconnect() correctly.
>
> - Dave
>
>
>
-- Matthew Dharm Home: mdharm-usb@one-eyed-alien.net Maintainer, Linux USB Mass Storage DriverWay to go, lava boy. -- Stef to Greg User Friendly, 3/26/1998
This archive was generated by hypermail 2b29 : Sun Jul 07 2002 - 22:00:13 EST