From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754138AbdEQRg4 (ORCPT ); Wed, 17 May 2017 13:36:56 -0400 Received: from ud10.udmedia.de ([194.117.254.50]:59152 "EHLO mail.ud10.udmedia.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753542AbdEQRgu (ORCPT ); Wed, 17 May 2017 13:36:50 -0400 Date: Wed, 17 May 2017 19:36:46 +0200 From: Markus Trippelsdorf To: linux-kernel@vger.kernel.org Cc: fweimer@redhat.com, Peter Zijlstra , Thomas Gleixner Subject: commit cfafcd117 "futex: Rework futex_lock_pi() to use rt_mutex_*_proxy_lock()" causes glibc nptl/tst-robustpi8 failure Message-ID: <20170517173646.GA281@x4> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Since: commit cfafcd117da0216520568c195cb2f6cd1980c4bb Author: Peter Zijlstra Date: Wed Mar 22 11:35:58 2017 +0100 futex: Rework futex_lock_pi() to use rt_mutex_*_proxy_lock() glibc's nptl/tst-robustpi8 testcase fails: glibc-build % ./nptl/tst-robustpi8 tst-robustpi8: ../nptl/pthread_mutex_lock.c:424: __pthread_mutex_lock_full: Assertion `INTERNAL_SYSCALL_ERRNO (e, __err) != ESRCH || !robust' failed. pthread_mutex_lock.c: 415 if (INTERNAL_SYSCALL_ERROR_P (e, __err) 416 && (INTERNAL_SYSCALL_ERRNO (e, __err) == ESRCH 417 || INTERNAL_SYSCALL_ERRNO (e, __err) == EDEADLK)) 418 { 419 assert (INTERNAL_SYSCALL_ERRNO (e, __err) != EDEADLK 420 || (kind != PTHREAD_MUTEX_ERRORCHECK_NP 421 && kind != PTHREAD_MUTEX_RECURSIVE_NP)); 422 /* ESRCH can happen only for non-robust PI mutexes where 423 the owner of the lock died. */ 424 assert (INTERNAL_SYSCALL_ERRNO (e, __err) != ESRCH || !robust); During bisection the commit above hangs the machine when I run the testcase. See: https://sourceware.org/bugzilla/show_bug.cgi?id=21487 -- Markus