linux-kernel - Re: [PATCH 2/2] x86/xen: Disable DMI parsing in Xen kernel.

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] [day] [month] [year] [list]

Date:	Thu, 28 Feb 2008 11:44:34 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Ian Campbell <ijc@...lion.org.uk>
Cc:	linux-kernel@...r.kernel.org, Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...hat.com>,
	"H. Peter Anvin" <hpa@...or.com>,
	Jeremy Fitzhardinge <jeremy@...p.org>,
	Mark McLoughlin <markmc@...hat.com>,
	Alexander van Heukelum <heukelum@...tmail.fm>
Subject: Re: [PATCH 2/2] x86/xen: Disable DMI parsing in Xen kernel.


* Ian Campbell <ijc@...lion.org.uk> wrote:

> > > Looks like the only sane solution will be to mark regions between 
> > > 640K-1M reserved early on in boot.
> > 
> > and as luck has it, such a patch from Alexander van Heukelum has 
> > been put into x86.git#testing just yesterday.
> > 
> > So ... could you try x86.git#testing - does it work out of box? Is 
> > the reservation early enough to prevent pagetables be allocated in 
> > weird places?
> 
> That patch is 64 bit only and also I'm not sure what EBDA looks like 
> to a Xen domU (I expect it doesn't exist). I'll give it a go but I'm 
> not hopeful.

it was requested to be unified to 32 bit as well already - no patch yet. 
I'd gladly take a patch that does it - it fixing 32-bit Xen guests would 
be an added bonus. Perhaps this all should be done by injecting a very 
eary e820 filter instead of reserving it later on? 640k..1M being 
special is a deep PC legacy, i doubt we'll ever recover from it ;-)

	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/