This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug nptl/16657] Lock elision breaks pthread_mutex_destroy
- From: "jmbnyc at gmail dot com" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sourceware dot org
- Date: Thu, 03 Jul 2014 03:24:21 +0000
- Subject: [Bug nptl/16657] Lock elision breaks pthread_mutex_destroy
- Auto-submitted: auto-generated
- References: <bug-16657-131 at http dot sourceware dot org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=16657
--- Comment #24 from Jeffrey M. Birnbaum <jmbnyc at gmail dot com> ---
Thanks Andi.
I would like to create a simple test case (the code is certainly quite simple)
but it might be hard to "make it happen" without additional scheduler pressure
(might have to manufacture). Also, I don't see it fail all of the time. And the
odd thing is that when it fails, it will fail continuously. I wonder if it
might be code alignment issue where depending on how stuff is arranged I get
fail or no fail. Lastly, more evidence is that the only system the code fails
on is glibc 2.18 plus Haswell. Can't seem to repro on various other machines
(ivy and sandy).
Regardless, I will work on a test case because I know what I observe is a
scenario where try_lock fails in the case where another thread had the lock and
then released it.
--
You are receiving this mail because:
You are on the CC list for the bug.