Re: How to prevent a mutex being _enter()ed from being _destroy()ed?

[Edgar Fuß <ef%math.uni-bonn.de@localhost>]

> The unp_gc thread assumes that holding a reference to the associated
> struct file, by incrementing f_count, prevents the socket from being
> freed.  Certainly that prevents closef from calling fo_close, which
> for a socket is soo_close, which calls soclose, which calls sofree,
> which calls soput.
Looks like this is not true. Maybe a race that makes different threads see 
different values of f_count?