From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 115077 invoked by alias); 13 Jun 2018 08:43:06 -0000 Mailing-List: contact libc-alpha-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: libc-alpha-owner@sourceware.org Received: (qmail 86631 invoked by uid 89); 13 Jun 2018 08:41:38 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.2 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS autolearn=ham version=3.3.2 spammy=smt, Hx-languages-length:892 X-HELO: mx1.redhat.com Subject: Re: [PATCH] Fix race in pthread_mutex_lock while promoting to PTHREAD_MUTEX_ELISION_NP [BZ #23275] To: Stefan Liebler , GNU C Library Cc: Torvald Riegel , Carlos O'Donell References: From: Florian Weimer Message-ID: <4851b1b3-2fd5-75c2-cc5e-68519e373df2@redhat.com> Date: Wed, 13 Jun 2018 08:43:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2018-06/txt/msg00291.txt.bz2 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