[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: assertion failure in the glibc
From: |
Samuel Thibault |
Subject: |
Re: assertion failure in the glibc |
Date: |
Thu, 28 Aug 2014 12:53:27 +0200 |
User-agent: |
Mutt/1.5.21+34 (58baf7c9f32f) (2010-12-30) |
Justus Winter, le Thu 28 Aug 2014 12:04:24 +0200, a écrit :
> Quoting Samuel Thibault (2014-08-27 21:53:39)
> > Justus Winter, le Mon 05 May 2014 14:10:48 +0200, a écrit :
> > > I believe I have found two problems in the glibc.
> > >
> > > 1. hurd_check_cancel takes 'lock', and then asserts that
> > > 'critical_section_lock' is not taken. However, hurd_thread_cancel
> > > first takes 'critical_section_lock' and then 'lock'. This program
> > > demonstrates this by spinning on both functions.
> >
> > Indeed, it's another instance of the issue worked around in
> > t/thread-cancel. Roland, this is the reproducer you were asking for in
> >
> > http://lists.gnu.org/archive/html/bug-hurd/2006-08/msg00019.html
>
> This problem also blocks a patch I have that introduces more
> fine-graded locking into libpager (or libports...? or both...).
I have commited it to the debian libc, to appear in 2.19-11.
Samuel