From: Josh Poimboeuf <jpoimboe@redhat.com>
To: "Woodhouse, David" <dwmw@amazon.co.uk>
Cc: "tglx@linutronix.de" <tglx@linutronix.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"peterz@infradead.org" <peterz@infradead.org>,
"arjan@linux.intel.com" <arjan@linux.intel.com>,
"mingo@kernel.org" <mingo@kernel.org>,
"torvalds@linux-foundation.org" <torvalds@linux-foundation.org>,
"tim.c.chen@linux.intel.com" <tim.c.chen@linux.intel.com>,
"ak@linux.intel.com" <ak@linux.intel.com>,
"pjt@google.com" <pjt@google.com>, "bp@alien8.de" <bp@alien8.de>,
"dave.hansen@intel.com" <dave.hansen@intel.com>,
"jikos@kernel.org" <jikos@kernel.org>,
"thomas.lendacky@amd.com" <thomas.lendacky@amd.com>,
"gregkh@linux-foundation.org" <gregkh@linux-foundation.org>
Subject: Re: x86: Meltdown/Spectre_v2 status
Date: Mon, 15 Jan 2018 08:28:28 -0600 [thread overview]
Message-ID: <20180115142828.wgytctikk7qvrvg6@treble> (raw)
In-Reply-To: <1515844512.22302.543.camel@amazon.co.uk>
On Sat, Jan 13, 2018 at 11:55:17AM +0000, Woodhouse, David wrote:
> FWIW we've done a backport of the sysfs/vulnerability and retpoline
> parts to 4.9, including cherry-picking a few earlier needed commits:
> http://git.infradead.org/retpoline-stable.git/shortlog/refs/heads/linux-4.9.y
>
> Josh, I'd very much appreciate your eyes on my objtool-related
> backports — both your retpoline-specific patches, as well as the
> .discard.* bits they depended on. Thanks.
>
> Bringing ASM_CALL_CONSTRAINT in as-is seemed like the same thing to do
> too.
The objtool-related backports look good.
--
Josh
next prev parent reply other threads:[~2018-01-15 14:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-12 21:44 x86: Meltdown/Spectre_v2 status Thomas Gleixner
2018-01-12 22:48 ` Josh Poimboeuf
2018-01-13 11:55 ` Woodhouse, David
2018-01-15 14:28 ` Josh Poimboeuf [this message]
2018-01-15 14:57 ` Christoph Hellwig
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=20180115142828.wgytctikk7qvrvg6@treble \
--to=jpoimboe@redhat.com \
--cc=ak@linux.intel.com \
--cc=arjan@linux.intel.com \
--cc=bp@alien8.de \
--cc=dave.hansen@intel.com \
--cc=dwmw@amazon.co.uk \
--cc=gregkh@linux-foundation.org \
--cc=jikos@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=pjt@google.com \
--cc=tglx@linutronix.de \
--cc=thomas.lendacky@amd.com \
--cc=tim.c.chen@linux.intel.com \
--cc=torvalds@linux-foundation.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).