linux-kernel - Re: [PATCH 0/2] microcode: Do early microcode application during resume-from-RAM

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20170613055534.GB1911@light.dominikbrodowski.net>
Date:   Tue, 13 Jun 2017 07:55:34 +0200
From:   Dominik Brodowski <linux@...inikbrodowski.net>
To:     Borislav Petkov <bp@...en8.de>
Cc:     Henrique de Moraes Holschuh <hmh@....eng.br>,
        LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 0/2] microcode: Do early microcode application during
 resume-from-RAM

Boris,

On Mon, Jun 12, 2017 at 07:58:52PM +0200, Borislav Petkov wrote:
> From: Borislav Petkov <bp@...e.de>
> 
> Ok,
> 
> I think I've dreamt of a simple solution to the early microcode
> application deal with suspend-to-RAM. The commit message of patch 2
> should explain it in more detail. Patch 1 is a fix for 32-bit when the
> ramdisk is being relocated.
> 
> I'm still testing but it seems to work.

Nice job; works fine here.

Best,
	Dominik