From owner-freebsd-threads@freebsd.org  Fri Dec 15 22:12:31 2017
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 A823DE8DFFC
 for <freebsd-threads@mailman.ysv.freebsd.org>;
 Fri, 15 Dec 2017 22:12:31 +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 965776776F
 for <freebsd-threads@FreeBSD.org>; Fri, 15 Dec 2017 22:12:31 +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 vBFMCUO5010482
 for <freebsd-threads@FreeBSD.org>; Fri, 15 Dec 2017 22:12:31 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-threads@FreeBSD.org
Subject: [Bug 224362] 'mutex is on list' assertion failed on
 pthread_mutex_lock/pthread_mutex_unlock
Date: Fri, 15 Dec 2017 22:12:31 +0000
X-Bugzilla-Reason: AssignedTo
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Base System
X-Bugzilla-Component: threads
X-Bugzilla-Version: 9.2-RELEASE
X-Bugzilla-Keywords: patch
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: kib@FreeBSD.org
X-Bugzilla-Status: New
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-threads@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-224362-16-mc0A9IFrPh@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-224362-16@https.bugs.freebsd.org/bugzilla/>
References: <bug-224362-16@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
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.25
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: Fri, 15 Dec 2017 22:12:31 -0000

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

Konstantin Belousov <kib@FreeBSD.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |kib@FreeBSD.org

--- Comment #1 from Konstantin Belousov <kib@FreeBSD.org> ---
(In reply to Andrey Sploshnov from comment #0)
Do you really complain about 9.2 release, as indicated in the bug's metadat=
a ?=20
Reproduce the problem on HEAD or 11.1.

The mutex queue is maintained per thread, in other words it is thread-local,
and since only locked mutex is put or removed from the queue, your naive
spinlock does not add any protection.

The state of the mutex you printed is indeed strange, it has the lock owner=
 but
it is not on the queue, as the assertion claims.

--=20
You are receiving this mail because:
You are the assignee for the bug.=