linux-kernel - Re: [patch] Fix BIOS-e820 end address

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: <Pine.LNX.4.64.0709080904480.25942@fbirervta.pbzchgretzou.qr>
Date:	Sat, 8 Sep 2007 09:05:14 +0200 (CEST)
From:	Jan Engelhardt <jengelh@...putergmbh.de>
To:	"Keshavamurthy, Anil S" <anil.s.keshavamurthy@...el.com>
cc:	akpm@...l.org, Linux Kernel <linux-kernel@...r.kernel.org>,
	suresh.b.siddha@...el.com
Subject: Re: [patch] Fix BIOS-e820 end address


On Sep 8 2007 13:50, Keshavamurthy, Anil S wrote:
>--snip of boot message--
>BIOS-provided physical RAM map:
> BIOS-e820: 0000000000000000 - 00000000000a0000 (usable)
> BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
> BIOS-e820: 0000000000100000 - 000000007fe8cc00 (usable)
>----end snip---
>
>As you see from above the address 0000000000100000 is both
>shown as reserved and usable which is confusing.
>
>This patch fixes the BIOS-e820 end address.

If a segment should have size 0 (even possible?), your
patch makes it even more confusing.


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