From: Lee Jones <lee.jones@linaro.org>
To: stable@vger.kernel.org
Cc: zhengyejian@foxmail.com, Lee Jones <lee.jones@linaro.org>,
bigeasy@linutronix.de, bristot@redhat.com,
Darren Hart <dvhart@infradead.org>,
Heiko Carstens <heiko.carstens@de.ibm.com>,
Ingo Molnar <mingo@kernel.org>,
jdesfossez@efficios.com, juri.lelli@arm.com,
mathieu.desnoyers@efficios.com, rostedt@goodmis.org,
Sasha Levin <sashal@kernel.org>,
xlpang@redhat.com
Subject: [PATCH 4.9 0/3] Follow-up patch series to update Futex
Date: Thu, 11 Feb 2021 09:26:57 +0000 [thread overview]
Message-ID: <20210211092700.11772-1-lee.jones@linaro.org> (raw)
A potential coding issue was:
Reported-by: Zheng Yejian <zhengyejian@foxmail.com>
This set should solve it.
Peter Zijlstra (1):
futex: Change locking rules
Thomas Gleixner (2):
futex: Ensure the correct return value from futex_lock_pi()
futex: Cure exit race
kernel/futex.c | 233 +++++++++++++++++++++++++++++++++++++++----------
1 file changed, 189 insertions(+), 44 deletions(-)
Cc: bigeasy@linutronix.de
Cc: bristot@redhat.com
Cc: Darren Hart <dvhart@infradead.org>
Cc: dvhart@infradead.org
Cc: Heiko Carstens <heiko.carstens@de.ibm.com>
Cc: Ingo Molnar <mingo@kernel.org>
Cc: jdesfossez@efficios.com
Cc: juri.lelli@arm.com
Cc: mathieu.desnoyers@efficios.com
Cc: rostedt@goodmis.org
Cc: Sasha Levin <sashal@kernel.org>
Cc: stable@vger.kernel.org
Cc: xlpang@redhat.com
--
2.25.1
next reply other threads:[~2021-02-11 9:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-11 9:26 Lee Jones [this message]
2021-02-11 9:26 ` [PATCH 1/3] futex: Ensure the correct return value from futex_lock_pi() Lee Jones
2021-02-11 9:26 ` [PATCH 2/3] futex: Change locking rules Lee Jones
2021-02-11 9:27 ` [PATCH 3/3] futex: Cure exit race Lee Jones
2021-02-11 14:22 ` [PATCH 4.9 0/3] Follow-up patch series to update Futex Greg KH
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=20210211092700.11772-1-lee.jones@linaro.org \
--to=lee.jones@linaro.org \
--cc=bigeasy@linutronix.de \
--cc=bristot@redhat.com \
--cc=dvhart@infradead.org \
--cc=heiko.carstens@de.ibm.com \
--cc=jdesfossez@efficios.com \
--cc=juri.lelli@arm.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=mingo@kernel.org \
--cc=rostedt@goodmis.org \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=xlpang@redhat.com \
--cc=zhengyejian@foxmail.com \
--subject='Re: [PATCH 4.9 0/3] Follow-up patch series to update Futex' \
/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
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).