linux-kernel - Re: [PATCH] x86: tidy e820 output

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]

Date:	Wed, 22 Sep 2010 16:12:13 -0700 (PDT)
From:	David Rientjes <rientjes@...gle.com>
To:	"H. Peter Anvin" <hpa@...or.com>
cc:	Bjorn Helgaas <bjorn.helgaas@...com>,
	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...hat.com>, x86@...nel.org,
	Yinghai Lu <yinghai@...nel.org>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] x86: tidy e820 output

On Wed, 22 Sep 2010, H. Peter Anvin wrote:

> > This patch is going to break our userspace parsing scripts if you change 
> > the output format.  Admittedly, we're probably one of the few users who 
> > actually parses this output, but we do have reasons to do it for our 
> > firmware.  If there was some improvement being introduced here, we'd 
> > happily handle multiple regexs (we constantly add new patterns when new 
> > kernels are released), but I'm not seeing how this is better.
> 
> Kernel messages are not an ABI or API.
> 
> The user space API for this stuff is /sys/firmware/memmap.
> 

I'm referring to using [start, start + addr - 1] in the output, like 
/sys/firmware/memmap does, as opposed to [start, start + addr].  Is it not 
valuable to include the actual e820 map in some way, especially when you 
have your own BIOS?  We've always used this output since it isn't 
available later.

Another use of this information that people may already be using it for is 
ensuring the memmap= on the command line is parsed correctly.

So, again, I'm looking for the benefit here in this patch and it's not 
immediately apparent to me.
--
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/