Am Dienstag, 12. August 2003 22:17 schrieb Alan Stern:
> On Tue, 12 Aug 2003, Oliver Neukum wrote:
>
> > Am Dienstag, 12. August 2003 17:57 schrieb Alan Stern:
> > >
> > > Maybe it's an attempt to protect against the "device-morphed" possibility.
> > > I'm planning a re-write of that whole area. For now, it would probably be
> > > okay to remove the down_read() and up_read() in usb_reset_device().
> >
> > No, it is a guard against probe() which is bound to fail during a reset.
>
> But Andries's problem is that now reset is bound to fail during probe().
>
> What probe() does it protect against? Are you concerned that a driver
> bound to one interface might reset the device while another interface is
> being probed?
Yes, exactly. Probing, resetting and changing configurations must be mutually
exclusive. For doing a reset during probe a driver must call
usb_physical_reset_device(). I had thought of the problem when I last
changed this code path, but I overlooked this driver.
Regards
Oliver
-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
