On Tue, 2004-04-06 at 01:52, Oliver Neukum wrote: > 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.
Which part of On Mon, 2004-04-05 at 20:19, James Bottomley wrote: > Now, if the subsystem is going to garbage collect its own object as a > result of the other object disconnect, then it is responsible for > synchronising that with reference gets on its own object. However, that > is easily achievable via *intra* subsystem synchronisation. didn't you understand? However, how a subsystem resolves this intra subsystem synchronisation is up to it ... and it doesn't have to do it with locks. So there are no exposed locks for this and no rules therefore, for how to use them. James ------------------------------------------------------- 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
