From: Yann Droneaud <ydroneaud@opteya.com>
To: stable@vger.kernel.org
Cc: peterz@infradead.org, hpa@zytor.com, mingo@kernel.org,
tglx@linutronix.de, torvalds@linux-foundation.org,
linux-kernel@vger.kernel.org, x86@kernel.org,
ydroneaud@opteya.com
Subject: [-stable] perf/x86: Fix copy_from_user_nmi() return if range is not ok
Date: Tue, 08 Sep 2015 10:20:32 +0200 [thread overview]
Message-ID: <1441700432.19941.38.camel@opteya.com> (raw)
In-Reply-To: <tip-ebf2d2689de551d90965090bb991fc640a0c0d41@git.kernel.org>
Hi,
I believe commit ebf2d2689de551d90965090bb991fc640a0c0d41
("perf/x86: Fix copy_from_user_nmi() return if range is not ok")
should be applied to stable kernels starting from v3.13.y up to v4.1.y.
Regards.
--
Yann Droneaud
OPTEYA
next parent reply other threads:[~2015-09-08 8:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1435001923-30986-1-git-send-email-ydroneaud@opteya.com>
[not found] ` <tip-ebf2d2689de551d90965090bb991fc640a0c0d41@git.kernel.org>
2015-09-08 8:20 ` Yann Droneaud [this message]
2015-09-28 13:18 ` [-stable] perf/x86: Fix copy_from_user_nmi() return if range is not ok Luis Henriques
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=1441700432.19941.38.camel@opteya.com \
--to=ydroneaud@opteya.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=x86@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 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).