linux-kernel - Re: [PATCH 1/2] x86 boot: add E820_RESVD

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: <20080630191628.GA15366@elte.hu>
Date:	Mon, 30 Jun 2008 21:16:28 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Yinghai Lu <yhlu.kernel@...il.com>
Cc:	"Huang, Ying" <ying.huang@...el.com>,
	"H. Peter Anvin" <hpa@...or.com>, andi@...stfloor.org,
	mingo@...hat.com, tglx@...utronix.de, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/2] x86 boot: add E820_RESVD_KERN


* Yinghai Lu <yhlu.kernel@...il.com> wrote:

> > For find_e820_area, this is safe enough. But what about conflict 
> > between setup_data and ebda or ramdisk?
> 
> can you have setup_data and ebda at the same time?
> 
> setup_data and ramdisk should be ok, because bootloader is supposed to 
> make them not to be conflicts.

the more sanity checks we do before relying on some crutial data, the 
better. It's easier to panic or sanitize data in some structured way and 
complain about it in the syslog than to let things get corrupted. Boot 
loaders are ... not unknown to be have bugs too, at times.

	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/