linux-kernel - Re: [PATCH -mm -v3] x86 boot : export boot

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: <m1abo8d3jk.fsf@ebiederm.dsl.xmission.com>
Date:	Mon, 17 Dec 2007 21:34:23 -0700
From:	ebiederm@...ssion.com (Eric W. Biederman)
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	Greg KH <greg@...ah.com>, "Huang, Ying" <ying.huang@...el.com>,
	akpm@...ux-foundation.org, Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...hat.com>, Andi Kleen <ak@...e.de>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH -mm -v3] x86 boot : export boot_params via sysfs

"H. Peter Anvin" <hpa@...or.com> writes:

> This is directly analogous to how we treat identity information in IDE, or PCI
> configuration space -- some fields are pre-digested, but the entire raw
> information is also available.

Add to that a totally unchanged value can just be easier to get correct.

Still the kexec code as much as it can should not look there, as we may
get the same basic information in a couple of different ways.

EFI memmap vs. e820 for example.  If/when that is the case /sbin/kexec
should get the information and spit it out into whatever format makes
sense for the destination kernel.  My sense is just passing through
values is brittleness where we don't want it.

However I think being able to get at the raw boot information overall
sounds useful.  I just don't know if it is generally useful or just
useful when debugging bootloaders though.

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