From: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
To: Borislav Petkov <bp@alien8.de>
Cc: LKML <linux-kernel@vger.kernel.org>, X86 ML <x86@kernel.org>
Subject: Re: [PATCH 0/2] x86/microcode/amd: Do not overwrite specific patch levels
Date: Sat, 26 Mar 2016 20:31:57 -0300 [thread overview]
Message-ID: <20160326233157.GA11398@khazad-dum.debian.net> (raw)
In-Reply-To: <1435781656-1890-1-git-send-email-bp@alien8.de>
On Wed, 01 Jul 2015, Borislav Petkov wrote:
> Certain patch levels supplied by the BIOS should not be upgraded and
> overwritten by the microcode loader because doing so leaves the system
> dead in the water.
>
> The two below provide for filtering out those levels and avoiding the
> update, thereby making those patch levels final.
>
> Borislav Petkov (2):
> x86/microcode/amd: Extract current patch level read to a function
> x86/microcode/amd: Do not overwrite final patch levels
This patchset looks like it is pretty much a requirement for any distro that
ships AMD microcode updates... Maybe the two commits should be sent to
-stable, now that they have seen lots of testing in mainline 4.4.x as well
as SuSE kernels?
--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
Henrique Holschuh
next prev parent reply other threads:[~2016-03-26 23:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-01 20:14 Borislav Petkov
2015-07-01 20:14 ` [PATCH 1/2] x86/microcode/amd: Extract current patch level read to a function Borislav Petkov
2015-07-01 20:14 ` [PATCH 2/2] x86/microcode/amd: Do not overwrite final patch levels Borislav Petkov
2015-07-09 15:03 ` [PATCH 0/2] x86/microcode/amd: Do not overwrite specific " Henrique de Moraes Holschuh
2015-07-10 10:11 ` Borislav Petkov
2015-07-10 15:12 ` Henrique de Moraes Holschuh
2016-03-26 23:31 ` Henrique de Moraes Holschuh [this message]
2016-03-27 8:31 ` Borislav Petkov
2016-03-27 12:32 ` Henrique de Moraes Holschuh
2016-03-27 15:47 ` Borislav Petkov
2016-05-02 15:30 ` Borislav Petkov
2016-05-06 12:43 ` Henrique de Moraes Holschuh
2016-05-06 13:23 ` Borislav Petkov
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=20160326233157.GA11398@khazad-dum.debian.net \
--to=hmh@hmh.eng.br \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®