| 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
| ||
|
Date: Mon, 8 Sep 2008 18:01:25 +0100 From: Alan Cox <alan@...rguk.ukuu.org.uk> To: Jeremy Fitzhardinge <jeremy@...p.org> Cc: Nick Piggin <nickpiggin@...oo.com.au>, 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 On Mon, 08 Sep 2008 09:47:07 -0700 Jeremy Fitzhardinge <jeremy@...p.org> wrote: > 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. Or that its hitting stuff that doesn't kill the OS... What has the vendor had to say and if they are not being helpful has anyone considered delivered them a report of the corruption and trace info by say registered post with a suggestion that they might now be knowingly exposing customers to unneccessary risk through their inaction ... Alan -- 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/
Powered by blists - more mailing lists