linux-kernel - Re: Windows side agrees that lowmem corruption is a problem too

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: <20100608190848.GD25985@elte.hu>
Date:	Tue, 8 Jun 2010 21:08:48 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	Yuhong Bao <yuhongbao_386@...mail.com>,
	linux-kernel@...r.kernel.org, gregkh@...e.de
Subject: Re: Windows side agrees that lowmem corruption is a problem too


* H. Peter Anvin <hpa@...or.com> wrote:

> On 06/08/2010 11:28 AM, Yuhong Bao wrote:
> > 
> > Adding mingo and gregkh to CC list.
> >> Remember the lowmem corruption problems that lead the code that displays this to be added to Linux:> AMI BIOS detected: BIOS may corrupt low RAM, working around it.> which was IMO way too broad. Good news, the Windows side agree that this is a problem too:> http://www.microsoft.com/whdc/system/platform/firmware/mem-corrupt.mspx>> Yuhong Bao
> > 
> 
> Hardly "way too broad".  I'm starting to think we should enable it
> unconditionally, given the number of machines which have exhibited that
> problem.  As shown in the whitepaper, Vista/Win7 even avoid using
> < 1 MB for a lot of things, presumably for this reason.
> 
> If it only was suspend, it would be one thing, but from what I've seen
> it has been known to happen at other times too (e.g. HDMI cable insertion!)

Yep, patterns of some silly OSD bitmap showed up in one of the corruption - 
firmware displaying a 'you inserted a cable' kind of icon somewhere and 
messing up the SMM code or so ...

I agree that dis-using <1M by default is probably the sanest option.

	Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/