From: Alexander Sergeyev <sergeev917@gmail.com>
To: David Woodhouse <dwmw@amazon.co.uk>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, Kyle Huey <me@kylehuey.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Levin, Alexander (Sasha Levin)" <alexander.levin@verizon.com>,
Peter Zijlstra <peterz@infradead.org>,
linux-kernel@vger.kernel.org
Subject: update spectre v2 microcodes blacklist
Date: Sat, 10 Feb 2018 15:31:23 +0300 [thread overview]
Message-ID: <20180210123123.GA19396@localhost.localdomain> (raw)
Hello,
Intel released an updated microcode revision guidance [1] (8 Feb). The link is
available in press-release [2], but it's quite easy to miss.
Some microcode revisions that were blacklisted before are now tested and
pronounced production-ready:
> Lines with “***” were previously recommended to discontinue use.
> Subsequent testing by Intel has determined that these were unaffected
> by the stability issues and have been re-released without
> modification.
I didn't fully match the updated revision guidance and spectre_bad_microcodes[]
in arch/x86/kernel/cpu/intel.c, but at least microcode 0xc2 for intel skylakes
should not be blacklisted anymore.
The update is also revelant to a recent blacklist backport to 4.9-stable:
https://patchwork.kernel.org/patch/10209021/
[1] https://newsroom.intel.com/wp-content/uploads/sites/11/2018/02/microcode-update-guidance.pdf
[2] https://newsroom.intel.com/news/security-issue-update-progress-continues-firmware-updates/
next reply other threads:[~2018-02-10 12:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-10 12:31 Alexander Sergeyev [this message]
2018-02-10 17:14 ` update spectre v2 microcodes blacklist Alexander Sergeyev
2018-02-12 9:34 ` David Woodhouse
2018-02-12 13:56 ` Van De Ven, Arjan
2018-02-12 14:11 ` Alexander Sergeyev
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=20180210123123.GA19396@localhost.localdomain \
--to=sergeev917@gmail.com \
--cc=alexander.levin@verizon.com \
--cc=dwmw@amazon.co.uk \
--cc=gregkh@linuxfoundation.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=me@kylehuey.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--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