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 for Android: free password hash cracker in your pocket

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

Message-ID: <52b804e35d9e82a46b35409586475ee2@openmailbox.org>
Date:   Sat, 22 Oct 2016 14:16:41 +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


Patch does not compile.

I tried to add pci.h but did nothing.
I converted pci_read_config to pci_read_config_dword but again nothing.


On 2016-10-22 02:01, Borislav Petkov wrote:
> Do you have a way to trigger that one?
To be honest I can't say. My brother's machine(s) has random crashes 
from time to time. We suspect that this erratum is to blame. He must 
have kept some information at least from one of those crashes but there 
was no time to analyze them till now. Finding those logs on our disks 
needs a big effort but it will be done! We are willing to discover the 
trouble maker no matter what it takes. To do that the machine must be 
stripped off from all cards and then put on quarantine. Then we can 
connect it with a another machine with an RS-232 cable to see what is 
wrong. After that we must test it on a different motherboard we have. I 
think we have one with a BIOS from a different BIOS vendor. We will 
surely inform you on this one as we can't do such a patch. So we will 
focus on triggering this bug. One thing is sure, its BIOS has no 
workaround for that erratum.