public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Greg KH <greg@kroah.com>
Cc: "Huang, Ying" <ying.huang@intel.com>,
	akpm@linux-foundation.org, Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, Andi Kleen <ak@suse.de>,
	"Eric W. Biederman" <ebiederm@xmission.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH -mm -v2] x86 boot : export boot_params via sysfs
Date: Wed, 12 Dec 2007 09:54:12 -0800	[thread overview]
Message-ID: <47602044.9010104@zytor.com> (raw)
In-Reply-To: <20071212174613.GC16049@kroah.com>

Greg KH wrote:
> On Wed, Dec 12, 2007 at 04:59:51PM +0800, Huang, Ying wrote:
>> This patch export the boot parameters via sysfs. This can be used for
>> debugging and kexec.
>>
>> The files added are as follow:
>>
>> /sys/kernel/boot_params/data	: binary file for struct boot_params
>> /sys/kernel/boot_params/version	: boot protocol version
>>
>> This patch is based on 2.6.24-rc4-mm1 and has been tested on i386 and
>> x86_64 platoform.
>>
>> This patch is based on the Peter Anvin's proposal.
> 
> As outlined in a previous email, I object to the whole structure being
> exported to userspace as a binary blob.  Please change that.
> 

I would prefer to have the binary blob available; exported fields is 
possible too, of course.

This is a binary structure defined by protocol; in that way it's not 
significantly different from something passed from the firmware (in 
fact, it might very well *be* passed from the firmware.)  We have in the 
past found platform bugs by looking at the contents of the whole 
structure, e.g. to find that part of it has been inappropriately clobbered.

It is also in the form needed by e.g. kexec to operate.

	-hpa

  reply	other threads:[~2007-12-12 18:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-12  8:59 [PATCH -mm -v2] x86 boot : export boot_params via sysfs Huang, Ying
2007-12-12 17:46 ` Greg KH
2007-12-12 17:54   ` H. Peter Anvin [this message]
2007-12-12 18:59     ` Greg KH
2007-12-12 19:05       ` H. Peter Anvin
2007-12-12 22:21         ` Greg KH
2007-12-12 22:37           ` H. Peter Anvin
2007-12-12 22:43           ` Randy Dunlap
2007-12-12 23:08             ` Eric W. Biederman
2007-12-12 22:52           ` Eric W. Biederman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=47602044.9010104@zytor.com \
    --to=hpa@zytor.com \
    --cc=ak@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=ebiederm@xmission.com \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=ying.huang@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox