From owner-freebsd-threads@FreeBSD.ORG  Thu Oct 28 22:49:29 2004
Return-Path: <owner-freebsd-threads@FreeBSD.ORG>
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 DFB7616A4CE; Thu, 28 Oct 2004 22:49:29 +0000 (GMT)
Received: from mail.vicor-nb.com (bigwoop.vicor-nb.com [208.206.78.2])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id B4E6743D5D; Thu, 28 Oct 2004 22:49:29 +0000 (GMT)
	(envelope-from julian@elischer.org)
Received: from elischer.org (julian.vicor-nb.com [208.206.78.97])
	by mail.vicor-nb.com (Postfix) with ESMTP
	id 6A97B7A424; Thu, 28 Oct 2004 15:49:29 -0700 (PDT)
Message-ID: <41817778.4070801@elischer.org>
Date: Thu, 28 Oct 2004 15:49:28 -0700
From: Julian Elischer <julian@elischer.org>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3.1) Gecko/20030516
X-Accept-Language: en, hu
MIME-Version: 1.0
To: David Xu <davidxu@freebsd.org>
References: <41804394.7020306@elischer.org> <41804D8E.2030003@freebsd.org>
In-Reply-To: <41804D8E.2030003@freebsd.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
cc: Daniel Eischen <deischen@freebsd.org>
cc: threads@freebsd.org
cc: re@freebsd.org
cc: John Baldwin <jhb@freebsd.org>
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 <freebsd-threads.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-threads>,
	<mailto:freebsd-threads-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-threads>
List-Post: <mailto:freebsd-threads@freebsd.org>
List-Help: <mailto:freebsd-threads-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-threads>,
	<mailto:freebsd-threads-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Oct 2004 22:49:30 -0000

re, how about it?


David Xu wrote:

> Here is the cvs log:
>
> Revision  Changes    Path
>   1.58      +1 -0      src/lib/libpthread/thread/thr_create.c
>   1.14      +1 -1      src/lib/libpthread/thread/thr_find_thread.c
>   1.115     +27 -10    src/lib/libpthread/thread/thr_kern.c
>   1.119     +15 -11    src/lib/libpthread/thread/thr_private.h
>   1.81      +1 -2      src/lib/libpthread/thread/thr_sig.c
>
> Julian Elischer wrote:
>
>> David, do you have revision numbers of what needs to be MFC'd?
>>
>>
>> David Xu wrote:
>>
>>
>>> Daniel Eischen wrote:
>>>
>>>
>>>>> 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.
>>>>>  
>>>>
>>>>
>>>>
>>>> David and I recently fixed some races in pthread_join() and
>>>> pthread_exit() in -current libpthread.  Don't know if those
>>>> were responsible...
>>>>
>>>>
>>>>
>>>
>>> That fix should be MFCed ASAP.
>>>
>>>
>>>> Here's a test program that shows correct behavior with both
>>>> libc_r and libpthread in -current.
>>>>