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

Date:   Mon, 12 Jun 2017 19:58:52 +0200
From:   Borislav Petkov <bp@...en8.de>
To:     Dominik Brodowski <linux@...inikbrodowski.net>,
        Henrique de Moraes Holschuh <hmh@....eng.br>
Cc:     LKML <linux-kernel@...r.kernel.org>
Subject: [PATCH 0/2] microcode: Do early microcode application during resume-from-RAM

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.

Borislav Petkov (2):
  x86/microcode: Look for the initrd at the proper address on 32-bit
  x86/microcode/intel: Save pointer to ucode patch for early AP loading

 arch/x86/kernel/cpu/microcode/core.c  | 12 ++++++++++++
 arch/x86/kernel/cpu/microcode/intel.c | 25 +++++++++++++++++++++----
 2 files changed, 33 insertions(+), 4 deletions(-)

-- 
2.13.0