Date: Thu, 28 Oct 2004 19:08:40 -0400 (EDT) From: Daniel Eischen <deischen@freebsd.org> To: Julian Elischer <julian@elischer.org> Cc: John Baldwin <jhb@freebsd.org> Subject: Re: Infinite loop bug in libc_r on 4.x with condition variables a nd signals Message-ID: <Pine.GSO.4.43.0410281908000.5783-100000@sea.ntplx.net> In-Reply-To: <41817A08.9000706@elischer.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 28 Oct 2004, Julian Elischer wrote: > > > David Xu wrote: > > > Here is the cvs log: > > > > Revision Changes Path > > 1.58 +1 -0 src/lib/libpthread/thread/thr_create.c > > 1.14 +1 -1 src/lib/libpthread/thread/thr_find_thread.c > > 1.115 +27 -10 src/lib/libpthread/thread/thr_kern.c > > 1.119 +15 -11 src/lib/libpthread/thread/thr_private.h > > 1.81 +1 -2 src/lib/libpthread/thread/thr_sig.c > > commit message was: > 1. Move thread list flags into new separate member, and atomically > put DEAD thread on GC list, this closes a race between pthread_join > and thr_cleanup. > 2. Introduce a mutex to protect tcb initialization, tls allocation and > deallocation code in rtld seems no lock protection or it is broken, > under stress testing, memory is corrupted. > > > translates to: Yes, these look right. -- Dan Eischen
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.43.0410281908000.5783-100000>