Date: Thu, 28 Oct 2004 19:44:05 -0400 From: Ken Smith <kensmith@cse.Buffalo.EDU> To: Daniel Eischen <deischen@freebsd.org> Cc: David Xu <davidxu@freebsd.org> Subject: Re: Infinite loop bug in libc_r on 4.x with condition variables a nd signals Message-ID: <20041028234405.GC10099@electra.cse.Buffalo.EDU> In-Reply-To: <Pine.GSO.4.43.0410281936570.5783-100000@sea.ntplx.net> References: <20041028232946.GA10099@electra.cse.Buffalo.EDU> <Pine.GSO.4.43.0410281936570.5783-100000@sea.ntplx.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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 |
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20041028234405.GC10099>