Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Date:   Sat, 10 Feb 2018 15:31:23 +0300
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
Message-ID: <20180210123123.GA19396@localhost.localdomain>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
User-Agent: mtt
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

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/