linux-kernel - Re: [4.15 & 4.14 stable 00/12] Series to update microcode loading.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20180410154751.GA11614@kroah.com>
Date:   Tue, 10 Apr 2018 17:47:51 +0200
From:   Greg KH <gregkh@...uxfoundation.org>
To:     Ashok Raj <ashok.raj@...el.com>
Cc:     tglx@...utronix.de, linux-kernel@...r.kernel.org,
        stable@...r.kernel.org, bp@...e.de, thomas.lendacky@....com,
        arjan.van.de.ven@...el.com, asit.k.mallick@...el.com
Subject: Re: [4.15 & 4.14 stable 00/12] Series to update microcode loading.

On Fri, Apr 06, 2018 at 11:30:14AM -0700, Ashok Raj wrote:
> Hi Greg
> 
> Here is a series that addresses microcode loading stability issues post
> Spectre. All of them are simply cherry-picked and the patches themselves
> have the upstream commit ID's. 
> 
> I checked this for Intel platforms and thanks to Boris for checking
> on AMD platforms. 

Thanks, now queued up.

> I'm still working on a 4.9 backport, will send those once i get them to 
> work. stop_machine differences seem big enough that i might choose a 
> different approach for the 4.9 backport.

Ick, be careful, it's best to stick with almost identical code where
ever possible.  Otherwise you are almost always guaranteed to break
something :(

greg k-h