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: Tue, 5 Jun 2007 11:46:23 +0200 From: Andi Kleen <andi@...stfloor.org> To: "Eric W. Biederman" <ebiederm@...ssion.com> Cc: Yinghai Lu <yhlu.kernel@...il.com>, Alan Cox <alan@...rguk.ukuu.org.uk>, Justin Piszcz <jpiszcz@...idpixels.com>, Jesse Barnes <jbarnes@...tuousgeek.org>, Andi Kleen <andi@...stfloor.org>, linux-kernel@...r.kernel.org Subject: Re: Intel's response Linux/MTRR/8GB Memory Support / Why doesn't the kernel realize the BIOS has problems and re-map appropriately? > So the only safe thing we can do is not use memory that is not > write-back cached. That we can positively detect and is a > conservative action so if anything will work that will. Jesse wrote such a patch (or rather it limitted end_pfn), but it broke the X server for so far unknown reasons. -Andi - 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