The problem I see is that Oliver has been trying to avoid writing the line of code setting that pointer to zero when it's no longer in use. The problems he's describing will not show up when such lines exist in the driver.
Having refcount mechanisms doesn't help when the basic problem is keeping pointers around after they've become invalid (for whatever reason). ----- Original Message ----- From: "Alan Cox" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Cc: "Alan Cox" <[EMAIL PROTECTED]>; "David Brownell" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Tuesday, January 15, 2002 2:00 PM Subject: Re: [linux-usb-devel] Re: freeing urbs in completion handler - really seriously meant > > > The amount of bugs and crap refcounting has removed elsewhere in the kernel > > > and more importantly the amount of "if I do X very occasionally [list of > > > weirdness]" things that just went away testify to its value. > > > > That sounds sensible. However is the urb counted as referenced during the > > execution of the completion handler ? > > It would have to be. Basically nobody should have a pointer to an urb > if the refcount > 0, except at the point its set to zero and we kfree it _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
