On Saturday 19 January 2002 17:21, David Brownell wrote:
> > looking at the implementations of unlink in the HCDs, I noticed that
> > if the urb resubmits itself by the completion handler, unlinking it may
> > fail.
>
> Could you elaborate?
>
> > This means that some disconnect() methods are racy.
> > Who is buggy, the HCDs or the drivers ?
>
> Can't tell with what you've said so far. If the URB is unlinked
> and submitting it fails, then it's an obvious HCD bug.
The submitting succeeds, which is the problem.
CPUA: entering handler - - resubmitting
CPUB: usb_unlink_urb()
The driver assumes that after usb_unlink_urb() it could
safely free the URB, etc.
You might argue that the driver is buggy, yet there are many more
device drivers than HCDs, so writing a driver should be as easy as possible.
Regards
Oliver
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
