Date: Sun, 14 Nov 2004 19:31:54 +0800 From: David Xu <davidxu@freebsd.org> To: Brian Fundakowski Feldman <green@freebsd.org> Cc: Perforce Change Reviews <perforce@freebsd.org> Subject: Re: PERFORCE change 65074 for review Message-ID: <4197422A.4020905@freebsd.org> In-Reply-To: <20041114062748.GH997@green.homeunix.org> References: <200411140513.iAE5DOTv056478@repoman.freebsd.org> <20041114062748.GH997@green.homeunix.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Brian Fundakowski Feldman wrote: >On Sun, Nov 14, 2004 at 05:13:24AM +0000, David Xu wrote: > > >>http://perforce.freebsd.org/chv.cgi?CH=65074 >> >>Change 65074 by davidxu@davidxu_alona on 2004/11/14 05:12:40 >> >> 1. Fix a race between signal and umtx_unlock. a waiter >> may be resumed by signal and left or exited, heavily >> loaded test causes kernel to crash. >> 2. Use distributed queue locks instead of single giant >> lock. >> >> > >This sounds like it could be why recently valgrind has grown broken, >and is now entirely non-working and someimes crashes the system? > > > Both have bug, valgrind seems have lock leak, umtx code has race condition. David Xu
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4197422A.4020905>