From: Dirk Behme <dirk.behme@gmail.com>
To: Zefan Li <lizefan@huawei.com>
Cc: stable <stable@vger.kernel.org>
Subject: 3.4.106: futex: Wrong back port of 9e9aab5dbf?
Date: Sat, 08 Aug 2015 08:12:46 +0200 [thread overview]
Message-ID: <55C59DDE.5020908@gmail.com> (raw)
Hello,
from a private -stable review we think that the commit 9e9aab5dbf
("futex: Ensure get_futex_key_refs() always implies a barrier" [1]) is
not correctly back ported to 3.4.x:
The issue is that the memory barrier is introduced into
drop_futex_key_refs() function instead of get_futex_key_refs() function.
Additionally, we are unsure if the futex commits this commit is fixing
are really in < 3.4.106. I.e. we are unsure if this fix is needed at
all. Or at least if some additional futex commits are needed.
Do you like to check?
Best regards
Dirk
[1]
https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/?id=9e9aab5dbf6f13478cd996692ed9679af2404fc7
next reply other threads:[~2015-08-08 6:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-08 6:12 Dirk Behme [this message]
2015-09-07 8:43 ` 3.4.106: futex: Wrong back port of 9e9aab5dbf? Zefan Li
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=55C59DDE.5020908@gmail.com \
--to=dirk.behme@gmail.com \
--cc=lizefan@huawei.com \
--cc=stable@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.