From: Markus Trippelsdorf <markus@trippelsdorf.de>
To: linux-kernel@vger.kernel.org
Cc: fweimer@redhat.com, Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: commit cfafcd117 "futex: Rework futex_lock_pi() to use rt_mutex_*_proxy_lock()" causes glibc nptl/tst-robustpi8 failure
Date: Wed, 17 May 2017 19:36:46 +0200 [thread overview]
Message-ID: <20170517173646.GA281@x4> (raw)
Since:
commit cfafcd117da0216520568c195cb2f6cd1980c4bb
Author: Peter Zijlstra <peterz@infradead.org>
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
next reply other threads:[~2017-05-17 17:36 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-17 17:36 Markus Trippelsdorf [this message]
2017-05-17 17:50 ` commit cfafcd117 "futex: Rework futex_lock_pi() to use rt_mutex_*_proxy_lock()" causes glibc nptl/tst-robustpi8 failure Florian Weimer
2017-05-18 6:46 ` Peter Zijlstra
2017-05-18 6:57 ` Peter Zijlstra
2017-05-18 7:40 ` Peter Zijlstra
2017-05-18 8:04 ` Markus Trippelsdorf
2017-05-18 8:14 ` Peter Zijlstra
2017-05-18 8:12 ` Florian Weimer
2017-05-18 8:31 ` Peter Zijlstra
2017-05-18 8:34 ` Florian Weimer
2017-05-18 8:41 ` Peter Zijlstra
2017-05-18 8:42 ` Florian Weimer
2017-05-18 11:43 ` Peter Zijlstra
2017-05-18 12:30 ` Peter Zijlstra
2017-05-19 15:48 ` Peter Zijlstra
2017-05-19 16:07 ` Peter Zijlstra
2017-05-19 17:35 ` Markus Trippelsdorf
2017-05-22 20:04 ` [tip:locking/urgent] futex,rt_mutex: Fix rt_mutex_cleanup_proxy_lock() tip-bot for Peter Zijlstra
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170517173646.GA281@x4 \
--to=markus@trippelsdorf.de \
--cc=fweimer@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).