This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [PATCH] Fix race in pthread_mutex_lock while promoting to PTHREAD_MUTEX_ELISION_NP [BZ #23275]
- From: Florian Weimer <fweimer at redhat dot com>
- To: Stefan Liebler <stli at linux dot ibm dot com>, GNU C Library <libc-alpha at sourceware dot org>
- Cc: Torvald Riegel <triegel at redhat dot com>, Carlos O'Donell <carlos at redhat dot com>
- Date: Wed, 13 Jun 2018 10:41:34 +0200
- Subject: Re: [PATCH] Fix race in pthread_mutex_lock while promoting to PTHREAD_MUTEX_ELISION_NP [BZ #23275]
- References: <f3fc33e5-aa98-f772-a1bf-c02ddf9352c7@linux.ibm.com>
On 06/12/2018 04:24 PM, Stefan Liebler wrote:
The new testcase tst-mutex10 is triggering the race on s390x and intel.
Presumably also on power, but I don't have access to a power machine
with lock-elision. At least the code for power is the same as on the
other two architectures. Can somebody test it on power?
I tried the test case on a machine with:
Model: 2.0 (pvr 004d 0200)
Model name: POWER8 (raw), altivec supported
AT_HWCAP: true_le archpmu vsx arch_2_06 dfp ic_snoop smt mmu fpu
altivec ppc64 ppc32
AT_HWCAP2: htm-nosc vcrypto tar isel ebb dscr htm arch_2_07
Presumably, that should have lock elision support?
If I apply the test (and only the test) to commit
a745c837cb51c2efe8900740548cb68ec2a2f7ab, the resulting glibc does not
show a test failure.
Thanks,
Florian