Alan Stern wrote:
Calls to usb_unlink_urb() while the completion handler is running won't do anything until the handler has returned.
It still violates the API spec: there's no completion callback with an unlink status (-ECONNRESET, -ENOENT). It shouldn't masquerade as a call that behaved correctly (unlink status callback guaranteed).
... if a
completion handler calls usb_unlink_urb() for its own urb (following a resubmit, for example), the call will spin indefinitely. Device drivers should just be careful not to do this.
That's appropriate. - Dave ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
