From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Eric Biggers <ebiggers3@gmail.com>
Cc: stable@vger.kernel.org, Eric Biggers <ebiggers@google.com>,
Andrew Morton <akpm@linux-foundation.org>,
Andy Lutomirski <luto@amacapital.net>,
Andy Lutomirski <luto@kernel.org>, Borislav Petkov <bp@alien8.de>,
Fenghua Yu <fenghua.yu@intel.com>, Kevin Hao <haokexin@gmail.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Michael Halcrow <mhalcrow@google.com>,
Oleg Nesterov <oleg@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
Wanpeng Li <wanpeng.li@hotmail.com>,
Yu-cheng Yu <yu-cheng.yu@intel.com>,
kernel-hardening@lists.openwall.com,
Ingo Molnar <mingo@kernel.org>
Subject: Re: [PATCH] x86/fpu: Don't let userspace set bogus xcomp_bv
Date: Mon, 2 Oct 2017 20:58:50 +0200 [thread overview]
Message-ID: <20171002185850.GB30634@kroah.com> (raw)
In-Reply-To: <20171002180140.142854-1-ebiggers3@gmail.com>
On Mon, Oct 02, 2017 at 11:01:40AM -0700, Eric Biggers wrote:
> From: Eric Biggers <ebiggers@google.com>
>
> commit 814fb7bb7db5433757d76f4c4502c96fc53b0b5e upstream. Please apply
> to 4.13-stable and 4.9-stable.
Thanks for all of these backports, now queued up.
greg k-h
next prev parent reply other threads:[~2017-10-02 18:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-02 18:01 [PATCH] x86/fpu: Don't let userspace set bogus xcomp_bv Eric Biggers
2017-10-02 18:57 ` Patch "x86/fpu: Don't let userspace set bogus xcomp_bv" has been added to the 4.13-stable tree gregkh
2017-10-02 18:58 ` Patch "x86/fpu: Don't let userspace set bogus xcomp_bv" has been added to the 4.9-stable tree gregkh
2017-10-02 18:58 ` Greg Kroah-Hartman [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-10-02 18:04 [PATCH] x86/fpu: Don't let userspace set bogus xcomp_bv Eric Biggers
2017-10-02 18:10 Eric Biggers
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=20171002185850.GB30634@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=ebiggers3@gmail.com \
--cc=ebiggers@google.com \
--cc=fenghua.yu@intel.com \
--cc=haokexin@gmail.com \
--cc=kernel-hardening@lists.openwall.com \
--cc=luto@amacapital.net \
--cc=luto@kernel.org \
--cc=mhalcrow@google.com \
--cc=mingo@kernel.org \
--cc=oleg@redhat.com \
--cc=peterz@infradead.org \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=wanpeng.li@hotmail.com \
--cc=yu-cheng.yu@intel.com \
/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).