> 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?
- Re: How to prevent a mutex being _enter... Edgar Fuß
- Re: How to prevent a mutex being _... Taylor R Campbell
- Re: How to prevent a mutex bei... Edgar Fuß
- Re: How to prevent a mutex bei... Taylor R Campbell
- Re: How to prevent a mutex bei... Edgar Fuß
- Re: How to prevent a mutex bei... Edgar Fuß
- Re: How to prevent a mutex bei... Taylor R Campbell
- Re: How to prevent a mutex bei... Taylor R Campbell
- Re: How to prevent a mutex bei... Taylor R Campbell
- Re: How to prevent a mutex bei... Edgar Fuß
- Re: How to prevent a mutex being _enter()ed fro... Edgar Fuß
- Re: How to prevent a mutex being _enter()ed from being _... Robert Elz