linux-kernel - Re: [Lguest] lguest: unhandled trap

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: <48FCD585.4050107@zytor.com>
Date:	Mon, 20 Oct 2008 12:01:25 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Ian Campbell <Ian.Campbell@...citrix.com>
CC:	Ingo Molnar <mingo@...e.hu>, Jeremy Fitzhardinge <jeremy@...p.org>,
	Rusty Russell <rusty@...tcorp.com.au>,
	maluta_tiago@...oo.com.br, lguest@...abs.org,
	Thomas Gleixner <tglx@...utronix.de>,
	linux-kernel@...r.kernel.org
Subject: Re: [Lguest] lguest: unhandled trap

Ian Campbell wrote:
> 
> Wasn't there some concern about BIOSes which don't correctly reserve
> their DMI tables? Or don't even have e820 maps? H. Peter once said:
> 
>> It's pretty standard for 0xf0000...0x100000 to be marked RESERVED in
>> E820 on real hardware (including the system I'm typing on right now.)
>> It is so marked to indicate that hardware cannot be mapped into that
>> space.  However, you can't rely on this fact -- heck, you can't rely on
>> E820 even existing on a real machine.  I have specimens of real-life
>> machines that go both ways.
> 

Not only that, but the ACPI spec states explicitly that the ISA magic 
areas should be handled without relying on E820.

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