On Thu, 18 Dec 2003, Alan Stern wrote: > Here's the problem: So long as the interface's embedded struct device has > a nonzero refcount (which it does until usb_destroy_configuration), it > will hold a reference to its parent usb_device.
Correction. The struct device doesn't hold a reference to the parent usb_device. Rather, the struct device's embedded kobject holds a reference to the parent usb_device's embedded struct device's embedded kobject. It's a problem in cognitive dissonance. The child -> parent reference for struct devices only persists as long as they are registered in sysfs. But the corresponding child -> parent reference in their embedded kobjects lasts as long as the kobject does, even after it has been deregistered from sysfs. Alan Stern ------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
