From owner-freebsd-threads@freebsd.org  Mon Nov 30 19:16:44 2015
Return-Path: <owner-freebsd-threads@freebsd.org>
Delivered-To: freebsd-threads@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id EBA1DA3C128
 for <freebsd-threads@mailman.ysv.freebsd.org>;
 Mon, 30 Nov 2015 19:16:44 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id D86791EE4
 for <freebsd-threads@FreeBSD.org>; Mon, 30 Nov 2015 19:16:44 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id tAUJGiKn098848
 for <freebsd-threads@FreeBSD.org>; Mon, 30 Nov 2015 19:16:44 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-threads@FreeBSD.org
Subject: [Bug 204178] stress2 on arm64 thr1 hangs after printing pthread_join
 error
Date: Mon, 30 Nov 2015 19:16:45 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: threads
X-Bugzilla-Version: 11.0-CURRENT
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: martin@lispworks.com
X-Bugzilla-Status: New
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: Andrew@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-204178-16-oPWxWCRMIC@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-204178-16@https.bugs.freebsd.org/bugzilla/>
References: <bug-204178-16@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-threads@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Threading on FreeBSD <freebsd-threads.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/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: <https://lists.freebsd.org/mailman/listinfo/freebsd-threads>, 
 <mailto:freebsd-threads-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 30 Nov 2015 19:16:45 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204178

martin@lispworks.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |martin@lispworks.com

--- Comment #9 from martin@lispworks.com ---
(In reply to Andrew Turner from comment #5)
Aren't the locks in _thr_alloc only used by threads that call pthread_create? 
For the code at
https://svnweb.freebsd.org/base/user/pho/stress2/testcases/thr1/thr1.c, this
only happens sequentially from the main thread, so that suggests something went
wrong releasing the lock on the userland side (it shouldn't need to trap into
the kernel).

-- 
You are receiving this mail because:
You are on the CC list for the bug.