Infinite loop bug in libc_r on 4.x with condition variables a nd signals

Ken Smith kensmith at cse.Buffalo.EDU
Thu Oct 28 16:44:11 PDT 2004


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 at cse.buffalo.edu
  there, funny things are everywhere.   |
                      - Theodore Geisel |


More information about the freebsd-threads mailing list