From: Greg KH <gregkh@linuxfoundation.org>
To: "Srivatsa S. Bhat" <srivatsa@csail.mit.edu>
Cc: "Dave Hansen" <dave@sr71.net>,
catalin.marinas@arm.com, "Wanpeng Li" <kernellwp@gmail.com>,
"Andi Kleen" <ak@linux.intel.com>,
linux-tip-commits@vger.kernel.org,
"Piotr Luc" <piotr.luc@intel.com>, "Mel Gorman" <mgorman@suse.de>,
"Van De Ven, Arjan" <arjan.van.de.ven@intel.com>,
xen-devel <xen-devel@lists.xenproject.org>,
"Alexander Sergeyev" <sergeev917@gmail.com>,
"Brian Gerst" <brgerst@gmail.com>,
"Andy Lutomirski" <luto@kernel.org>,
MickaëlSalaün <mic@digikod.net>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Joe Konno" <joe.konno@linux.intel.com>,
"Laura Abbott" <labbott@fedoraproject.org>,
"Will Drewry" <wad@chromium.org>,
LKML <linux-kernel@vger.kernel.org>,
"Jia Zhang" <qianyue.zj@alibaba-inc.com>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Linus Torvalds" <torvalds@linux-foundation.org>,
"David Woodhouse" <dwmw@amazon.co.uk>,
srinidhir@vmware.com
Subject: Re: [RESEND] Spectre-v2 (IBPB/IBRS) and SSBD fixes for 4.4.y
Date: Tue, 7 Aug 2018 21:15:31 +0200 [thread overview]
Message-ID: <20180807191531.GA28682@kroah.com> (raw)
In-Reply-To: <824c77d3-93d8-fb90-6eb0-afa4aeef6644@csail.mit.edu>
On Tue, Aug 07, 2018 at 12:08:07PM -0700, Srivatsa S. Bhat wrote:
> Also, upstream commit e01e80634ecdde1 (fork: unconditionally clear
> stack on fork) applies cleanly on 4.14 stable, so it would be great to
> cherry-pick it to 4.14 stable as well.
It is already in the 4.14.60 release, did I somehow mess up the
backport?
thanks,
greg k-h
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2018-08-07 19:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-14 9:25 [RESEND] Spectre-v2 (IBPB/IBRS) and SSBD fixes for 4.4.y Srivatsa S. Bhat
2018-07-14 9:31 ` [PATCH 4.4.y 040/101] x86/xen: Zero MSR_IA32_SPEC_CTRL before suspend Srivatsa S. Bhat
2018-07-15 11:26 ` [RESEND] Spectre-v2 (IBPB/IBRS) and SSBD fixes for 4.4.y Greg KH
2018-07-16 8:02 ` Srivatsa S. Bhat
2018-07-23 11:26 ` Greg KH
2018-07-23 17:27 ` Srivatsa S. Bhat
2018-07-23 22:06 ` Jiri Kosina
2018-07-24 20:13 ` Srivatsa S. Bhat
2018-07-24 22:02 ` Jiri Kosina
2018-07-26 23:09 ` Kees Cook
2018-08-02 19:22 ` Srivatsa S. Bhat
2018-08-02 22:22 ` Kees Cook
2018-08-03 23:20 ` Srivatsa S. Bhat
2018-08-07 13:49 ` Greg KH
2018-08-07 19:08 ` Srivatsa S. Bhat
2018-08-07 19:15 ` Greg KH [this message]
2018-08-07 19:19 ` Srivatsa S. Bhat
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=20180807191531.GA28682@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=arjan.van.de.ven@intel.com \
--cc=brgerst@gmail.com \
--cc=catalin.marinas@arm.com \
--cc=dave@sr71.net \
--cc=dwmw@amazon.co.uk \
--cc=joe.konno@linux.intel.com \
--cc=kernellwp@gmail.com \
--cc=labbott@fedoraproject.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mgorman@suse.de \
--cc=mic@digikod.net \
--cc=piotr.luc@intel.com \
--cc=qianyue.zj@alibaba-inc.com \
--cc=sergeev917@gmail.com \
--cc=srinidhir@vmware.com \
--cc=srivatsa@csail.mit.edu \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=wad@chromium.org \
--cc=xen-devel@lists.xenproject.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).