From owner-freebsd-threads@FreeBSD.ORG Thu Oct 28 23:44:11 2004 Return-Path: Delivered-To: freebsd-threads@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B345E16A4CE; Thu, 28 Oct 2004 23:44:11 +0000 (GMT) Received: from electra.cse.Buffalo.EDU (electra.cse.Buffalo.EDU [128.205.32.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 53D8443D45; Thu, 28 Oct 2004 23:44:11 +0000 (GMT) (envelope-from kensmith@cse.Buffalo.EDU) Received: from electra.cse.Buffalo.EDU (kensmith@localhost [127.0.0.1]) i9SNi5Io010883; Thu, 28 Oct 2004 19:44:05 -0400 (EDT) Received: (from kensmith@localhost) by electra.cse.Buffalo.EDU (8.12.10/8.12.9/Submit) id i9SNi5AV010882; Thu, 28 Oct 2004 19:44:05 -0400 (EDT) Date: Thu, 28 Oct 2004 19:44:05 -0400 From: Ken Smith To: Daniel Eischen Message-ID: <20041028234405.GC10099@electra.cse.Buffalo.EDU> References: <20041028232946.GA10099@electra.cse.Buffalo.EDU> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i cc: re@freebsd.org cc: John Baldwin cc: Julian Elischer cc: threads@freebsd.org cc: Ken Smith cc: David Xu Subject: Re: Infinite loop bug in libc_r on 4.x with condition variables a nd signals X-BeenThere: freebsd-threads@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Threading on FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Oct 2004 23:44:11 -0000 On Thu, Oct 28, 2004 at 07:40:01PM -0400, Daniel Eischen wrote: > On Thu, 28 Oct 2004, Ken Smith wrote: > > > On Thu, Oct 28, 2004 at 03:49:28PM -0700, Julian Elischer wrote: > > > > > re, how about it? > > > > Give me an hour or two, yesterday was the first I saw of this so I > > need to research it a bit. Is that OK? > > > > > >>>>>FWIW, we are having (I think) the same problem on 5.3 with > > > >>>>>libpthread. The > > > >>>>> > > > >>>>>panic there is in the mutex code about an assertion failing > > > >>>>>because a thread > > > >>>>>is on a syncq when it is not supposed to be. > > > > Umm. Your patch changes only user-level code, correct? Please tell > > me you can only panic a debugging kernel with user-level code issues. > > User-level panic by some assertions in libpthread which are caused > by a race condition that this patch closes. > Thank you. We use the word 'panic' for too many things one of which is much scarier than others. -- Ken Smith - From there to here, from here to | kensmith@cse.buffalo.edu there, funny things are everywhere. | - Theodore Geisel |