> The point is that all the disconnection event does is inform a subsystem
> that the entity represented by the other object has gone. What it
> chooses to do with the information is up to it. It could set it's own
> connected object to degraded, never use the other object again and drop
> the reference. Or, it could simply ignore the indication and continue
> to use the other object (even though it will return errors for every
> operation).
Pure refcounting can never protect you against races with freeing objects.
The counters themselves must be protected. Try as you might you need
locks for that and rules on how this locks are to be used.
Regards
Oliver
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
