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

Message-ID: <4851A595.8070601@zytor.com>
Date:	Thu, 12 Jun 2008 15:39:17 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Paul Jackson <pj@....com>
CC:	yhlu.kernel@...il.com, andi@...stfloor.org, mingo@...e.hu,
	bwalle@...e.de, hannes@...urebad.de, ying.huang@...el.com,
	linux-kernel@...r.kernel.org, steiner@....com
Subject: Re: Confusions with reserve_early, reserve_bootmem, e820, efi, ...
 on x86_64

Paul Jackson wrote:
> 
> Reserving EBDA with EFI is fine by what little I know.
> 
> But the current code doesn't like it -- if the EFI memmap range is inside
> the EBDA range, then the reserve_early() routine panics with:
> 
>     "Overlapping early reservations"
> 
> Something needs tweaking here somehow ... and I'm not the one to know what.
> 

Right of course... in this particular case, one of the reservations is 
conservative "just in case" and the other is normative, but the code 
doesn't deal with that since it's potentially flagging a bug.

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