linux-kernel - Re: [PATCH 0 of 3] Low memory corruption detection and workaround

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: <48C5570B.7050109@goop.org>
Date:	Mon, 08 Sep 2008 09:47:07 -0700
From:	Jeremy Fitzhardinge <jeremy@...p.org>
To:	Nick Piggin <nickpiggin@...oo.com.au>
CC:	Alan Jenkins <alan-jenkins@...fmail.co.uk>,
	Ingo Molnar <mingo@...e.hu>, linux-kernel@...r.kernel.org,
	Hugh Dickens <hugh@...itas.com>,
	"H. Peter Anvin" <hpa@...or.com>,
	Rafał Miłecki <zajec5@...il.com>
Subject: Re: [PATCH 0 of 3] Low memory corruption detection and workaround

Nick Piggin wrote:
> Why not high memory as well? We put page tables there too...
>   

Well, the specific problem is that the BIOS appears to corrupt low
memory.  It might corrupt other memory anywhere, but that would be
pretty pathologically evil.  The assumption is that it gets away with it
because its memory that Windows doesn't otherwise use or something.

> (rant: why can we still buy non-ECC memory?)
>   

Well, it wouldn't help in this case.  It's not random hardware bit-flipping.

    J
--
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/