From: Cyrill Gorcunov <gorcunov@gmail.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Harvey Harrison <harvey.harrison@gmail.com>,
Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
Sam Ravnborg <sam@ravnborg.org>,
LKML <linux-kernel@vger.kernel.org>,
Jaswinder Singh Rajput <jaswinderlinux@gmail.com>
Subject: Re: [PATCH -tip] x86: headers - fix export private data to userspace
Date: Tue, 13 Jan 2009 21:56:08 +0300 [thread overview]
Message-ID: <20090113185608.GD14470@localhost> (raw)
In-Reply-To: <496CE36B.1030604@zytor.com>
[H. Peter Anvin - Tue, Jan 13, 2009 at 10:54:35AM -0800]
| Cyrill Gorcunov wrote:
| >
| > I was concerning more about lilo side, is it use this param.
| > So here is a link
| >
| > http://lists.linuxcoding.com/kernel/2006-q3/msg18665.html
| >
| > is seems LILO has it's own definition for COMMAND_LINE_SIZE.
| > On the other hand it touches boot protocol. Peter should know
| > if it safe to hide/change COMMAND_LINE_SIZE. Peter?
| >
|
| Current x86 kernels export the command line size through the bzImage
| header, and as such COMMAND_LINE_SIZE should not be used by userspace.
|
| I can't speak for other architectures.
|
| -hpa
|
| --
| H. Peter Anvin, Intel Open Source Technology Center
| I work for Intel. I don't speak on their behalf.
|
Thanks Peter!
- Cyrill -
next prev parent reply other threads:[~2009-01-13 18:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-13 18:34 [PATCH -tip] x86: headers - fix export private data to userspace Cyrill Gorcunov
2009-01-13 18:37 ` Harvey Harrison
2009-01-13 18:49 ` H. Peter Anvin
2009-01-13 18:52 ` Cyrill Gorcunov
2009-01-13 18:55 ` H. Peter Anvin
2009-01-13 19:00 ` Cyrill Gorcunov
2009-01-13 19:03 ` H. Peter Anvin
2009-01-13 19:12 ` Cyrill Gorcunov
2009-01-13 19:05 ` Harvey Harrison
2009-01-13 18:50 ` Cyrill Gorcunov
2009-01-13 18:54 ` H. Peter Anvin
2009-01-13 18:56 ` Cyrill Gorcunov [this message]
2009-01-14 19:42 ` H. Peter Anvin
2009-01-14 19:49 ` Cyrill Gorcunov
2009-01-14 20:05 ` Cyrill Gorcunov
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=20090113185608.GD14470@localhost \
--to=gorcunov@gmail.com \
--cc=harvey.harrison@gmail.com \
--cc=hpa@zytor.com \
--cc=jaswinderlinux@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=sam@ravnborg.org \
--cc=tglx@linutronix.de \
/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