linux-kernel - Re: [PATCH RFC] x86: check for and defend against BIOS memory corruption

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: <b170af450808290930x29f57941k57d2a08d89977ca2@mail.gmail.com>
Date:	Fri, 29 Aug 2008 18:30:51 +0200
From:	"Rafał Miłecki" <zajec5@...il.com>
To:	"Hugh Dickins" <hugh@...itas.com>
Cc:	"Alan Jenkins" <alan-jenkins@...fmail.co.uk>,
	"Alan Cox" <alan@...rguk.ukuu.org.uk>,
	"Jeremy Fitzhardinge" <jeremy@...p.org>,
	"Yinghai Lu" <yhlu.kernel@...il.com>,
	"Ingo Molnar" <mingo@...e.hu>, "H. Peter Anvin" <hpa@...or.com>,
	"Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH RFC] x86: check for and defend against BIOS memory corruption

2008/8/29 Hugh Dickins <hugh@...itas.com>:
> On Fri, 29 Aug 2008, Alan Jenkins wrote:
>> Rafał Miłecki wrote:
>> >
>> > I tried your patch anyway (after applying Jeremy's patch of course)
>> > and it doesn't seem to work. The only output is:
>> > scanning 2 areas for BIOS corruption
>> > after using s2ram. I do not get any
>> > Corrupted low memory at*
>> >
>> It seemed to work for me.  Did you remember to plug HDMI to trigger the
>> corruption before you used s2ram?
>
> I hope that's what got missed.

Ah, stupid mistake, sorry! Indeed, using HDMI and s2ram later works fine:

Corrupted low memory at ffff88000000be98 (be98 phys) = b02a000400000000
 [<ffffffff8020fc9c>] check_for_bios_corruption+0x94/0xa0

-- 
Rafał Miłecki