From: Ingo Molnar <mingo@elte.hu>
To: Tim Bird <tim.bird@am.sony.com>
Cc: linux kernel <linux-kernel@vger.kernel.org>,
linux-embedded <linux-embedded@vger.kernel.org>,
Matt Mackall <mpm@selenic.com>, "H. Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH] bootup: Add built-in kernel command line for x86
Date: Mon, 11 Aug 2008 21:10:12 +0200 [thread overview]
Message-ID: <20080811191012.GA16553@elte.hu> (raw)
In-Reply-To: <489A1844.3090502@am.sony.com>
* Tim Bird <tim.bird@am.sony.com> wrote:
> Add support for a built-in command line for x86 architectures. The
> Kconfig help gives the major rationale for this addition.
i have actually used a local hack quite similar to this to inject boot
options into bzImages via randconfig - so i would find this feature
rather useful.
a small observation:
> + /* append boot loader cmdline to builtin, unless builtin overrides it */
> + if (builtin_cmdline[0] != '!') {
> + strlcat(builtin_cmdline, " ", COMMAND_LINE_SIZE);
> + strlcat(builtin_cmdline, boot_command_line, COMMAND_LINE_SIZE);
> + strlcpy(boot_command_line, builtin_cmdline, COMMAND_LINE_SIZE);
> + } else {
> + strlcpy(boot_command_line, &builtin_cmdline[1],
> + COMMAND_LINE_SIZE);
> + }
the default branch changes existing command lines slightly: it appends a
space to them. This could break scripts that rely on the precise
contents of /proc/cmdline output. (i have some - they are arguably
dodgy)
Best would be to make it really apparent in the code that nothing
changes if this config option is not set. Preferably there should be no
extra code at all in that case.
Ingo
next prev parent reply other threads:[~2008-08-11 19:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-06 21:31 [PATCH] bootup: Add built-in kernel command line for x86 Tim Bird
2008-08-06 22:04 ` Robert Schwebel
2008-08-06 22:22 ` Tim Bird
2008-08-06 22:48 ` H. Peter Anvin
2008-08-06 22:52 ` Matt Mackall
2008-08-06 23:02 ` H. Peter Anvin
2008-08-06 23:00 ` Tim Bird
2008-08-06 23:03 ` H. Peter Anvin
2008-08-06 22:14 ` Matt Mackall
2008-08-06 22:31 ` Tim Bird
2008-08-06 22:48 ` Matt Mackall
2008-08-11 19:10 ` Ingo Molnar [this message]
2008-08-11 19:23 ` H. Peter Anvin
2008-08-11 22:40 ` Tim Bird
2008-08-12 19:52 ` [PATCH] bootup: Add built-in kernel command line for x86 (v2) Tim Bird
2008-08-15 14:03 ` Ingo Molnar
2008-08-15 14:12 ` Ingo Molnar
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=20080811191012.GA16553@elte.hu \
--to=mingo@elte.hu \
--cc=hpa@zytor.com \
--cc=linux-embedded@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpm@selenic.com \
--cc=tglx@linutronix.de \
--cc=tim.bird@am.sony.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;
as well as URLs for NNTP newsgroup(s).