From: Ben Hutchings <ben@decadent.org.uk>
To: Kevin Christopher <kevinc@vmware.com>, stable@vger.kernel.org
Subject: Re: Request security fix in -stable (upstream 2c33645d366d)
Date: Sun, 08 Oct 2017 22:09:03 +0100 [thread overview]
Message-ID: <1507496943.2677.95.camel@decadent.org.uk> (raw)
In-Reply-To: <577D8299.7030502@vmware.com>
[-- Attachment #1: Type: text/plain, Size: 946 bytes --]
On Wed, 2016-07-06 at 15:13 -0700, Kevin Christopher wrote:
> Stable maintainers -
>
> Have a request to merge an upstream security fix into stable branches.
> The change avoids a userlevel-induceable kernel #GP in perf/x86 when a
> hypervisor emulates older perfmon. The issue was originally seen and
> accepted as an upstream patch proposed by Amazon in 2015; the security
> implication when on a VMware hypervisor was recently reported.
>
> Upstream commit:
> (commit) 2c33645d366d13b969d936b68b9f4875b1fdddea
> (subject) perf/x86: Honor the architectural performance monitoring version
>
> A second commit fixes a trivial build issue introduced by the above commit:
> (commit) 6d6f2833bfbf296101f9f085e10488aef2601ba5
> (subject) perf/x86: Fix undefined shift on 32-bit kernels
[...]
Belatedly queued these up for 3.16.
Ben.
--
Ben Hutchings
compatible: Gracefully accepts erroneous data from any source
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2017-10-08 21:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-06 22:13 Request security fix in -stable (upstream 2c33645d366d) Kevin Christopher
2016-07-07 4:40 ` Willy Tarreau
2016-07-07 7:21 ` Peter Zijlstra
2016-07-07 8:28 ` Willy Tarreau
2017-10-08 21:09 ` Ben Hutchings [this message]
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=1507496943.2677.95.camel@decadent.org.uk \
--to=ben@decadent.org.uk \
--cc=kevinc@vmware.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.