> Here's a tiny patch that fixes a potential oops that drivers could
> cause in usb_unlink_urb() and usb_submit_urb().  I traced down a race
> condition that the visor driver was ending up calling usb_unlink_urb()
> after it had been removed, and the urb->dev->bus was removed.
> 
> What do people think?  Should this patch be added?

I almost submitted a patch like that this summer, but didn't
because I ran across some followon problems.  I forget
the details, but in principle it should be safe to guard against
such problems like this.

Clearly it's a bug if any driver still has a handle on a device
after it's been removed.  Enabling slab poisoning should
turn up such driver bugs.

- Dave



_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel

Reply via email to