Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 15 Dec 2017 22:12:31 +0000
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
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/>

next in thread | previous in thread | raw e-mail | index | archive | help
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.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-224362-16-mc0A9IFrPh>