linux-kernel - Re: Confusions with reserve_early, reserve_bootmem, e820, efi, ... on x86

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]

Message-Id: <1213318779.20431.3.camel@caritas-dev.intel.com>
Date:	Fri, 13 Jun 2008 08:59:39 +0800
From:	"Huang, Ying" <ying.huang@...el.com>
To:	Paul Jackson <pj@....com>
Cc:	Yinghai Lu <yhlu.kernel@...il.com>, Ingo Molnar <mingo@...e.hu>,
	Bernhard Walle <bwalle@...e.de>,
	Johannes Weiner <hannes@...urebad.de>,
	linux-kernel@...r.kernel.org, Jack Steiner <steiner@....com>
Subject: Re: Confusions with reserve_early, reserve_bootmem, e820, efi, ...
	on x86_64

On Thu, 2008-06-12 at 05:06 -0500, Paul Jackson wrote:
> Bernhard, Johannes, Huang, and Yinghai:
> 
> I am running into some complications with reserve_bootmem vs
> reserve_early, and a reserve_early of "EFI memmap" in the
> efi_reserve_early() routine conflicting with reserve_early of
> "BIOS reserved" in reserve_ebda_region().
> 
> This is on x86_64 arch, using Ingo's x86-latest, with possibly
> still buggy EFI firmware in a lab system I'm helping to develop.
> 
> I have three concerns:
> 
>  1) The find_overlapped_early() check called from reserve_early is
>     failing on my lab system , causing panic, when it tries to
>     register "EFI memmap" at addresses <0xe0660, 0xe0778> that
>     overlaps with the "BIOS reserved" early reserve at addresses
>     <0x9f000, 0x100000>

I think this can be resolved by avoiding memory area <0x9f000, 0x100000>
when allocating memory for EFI memory map in boot-loader.

Best Regards,
Huang Ying


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