linux-kernel - Re: [PATCH] x86/AMD: Apply erratum 688 on machines without a BIOS fix

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: <78e7e3b73f5ad8af44710a0e104301cb@openmailbox.org>
Date:   Mon, 24 Oct 2016 00:02:39 +0300
From:   sonofagun@...nmailbox.org
To:     Borislav Petkov <bp@...en8.de>
Cc:     linux-kernel@...r.kernel.org, Nikos Barkas <levelwol@...il.com>
Subject: Re: [PATCH] x86/AMD: Apply erratum 688 on machines without a BIOS fix

> In any case, I tested it on my ON-B0 box and it looked good.
Good to hear but something is still wrong on my laptop as nothing worked 
as expected :(

Since I have a working custom kernel including the fix from my original 
patch it was clear from boot that the last patched kernel did not touch 
the MSR we want to modify at all. The machine was slower compared with 
my kernel using the original patch. As I use the show_msr option, a 
quick look at the dmesg proved that easily. Nowadays that processors 
have many cores, I wonder if the kernel should report which CPU MSRs are 
displayed at dmesg.

Take your time to see what is wrong, we already have one working kernel 
for our machine :)