From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: julia@ni.com
Cc: linux-rt-users@vger.kernel.org, Steven Rostedt <rostedt@goodmis.org>
Subject: [v4.9 RT 0/6] futex backports
Date: Wed, 6 Jun 2018 15:31:25 +0200 [thread overview]
Message-ID: <20180606133131.7747-1-bigeasy@linutronix.de> (raw)
Hi Julia,
as mentioned in the stable meeting, here is the futex patch that was
missing in the v4.9 tree :)
The futex state in v4.9 was backported from a later kernel at the time
Peter made the patches. That is why all the fixes which were tagged
stable did not enter the v4.9 stable tree.
I had a "deadlock assert in glibc" from pthread_mutex_lock() which did
not make a lot of sense. After comparing the futex code in latest v4.9
and v4.14 I identified a few patches which should be backported.
I haven't seen the issue after applying the patches which follow as a
reply to this email. They apply on top of v4.9.98-rt76.
Sebastian
next reply other threads:[~2018-06-06 13:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-06 13:31 Sebastian Andrzej Siewior [this message]
2018-06-06 13:31 ` [PATCH 1/6] futex: Fix pi_state->owner serialization Sebastian Andrzej Siewior
2018-06-06 13:31 ` [PATCH 2/6] futex: Fix more put_pi_state() vs. exit_pi_state_list() races Sebastian Andrzej Siewior
2018-06-06 13:31 ` [PATCH 3/6] futex: Avoid violating the 10th rule of futex Sebastian Andrzej Siewior
2018-06-06 13:31 ` [PATCH 4/6] futex: Fix OWNER_DEAD fixup Sebastian Andrzej Siewior
2018-06-06 13:31 ` [PATCH 5/6] rtmutex: Make rt_mutex_futex_unlock() safe for irq-off callsites Sebastian Andrzej Siewior
2018-06-06 13:31 ` [PATCH 6/6] rcu: Suppress lockdep false-positive ->boost_mtx complaints Sebastian Andrzej Siewior
2018-06-06 18:23 ` [v4.9 RT 0/6] futex backports Steven Rostedt
2018-06-12 17:53 ` Julia Cartwright
2018-06-15 16:11 ` Sebastian Andrzej Siewior
2018-07-09 9:58 ` [PATCH RT 7/6] rcu: Do not include rtmutex_common.h unconditionally Sebastian Andrzej Siewior
2018-07-10 16:53 ` [PATCH RT 8/6] sched, tracing: Fix trace_sched_pi_setprio() for deboosting Sebastian Andrzej Siewior
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=20180606133131.7747-1-bigeasy@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=julia@ni.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=rostedt@goodmis.org \
/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).