From: Woody Suwalski <terraluna977@gmail.com>
To: Chris Metcalf <cmetcalf@tilera.com>
Cc: Pawel Moll <pawel.moll@arm.com>, Ingo Molnar <mingo@elte.hu>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Andrew Morton <akpm@linux-foundation.org>,
Rusty Russell <rusty@rustcorp.com.au>,
Stanislaw Gruszka <sgruszka@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] init: fix bug where environment vars can't be passed via boot args
Date: Sat, 07 Apr 2012 16:29:35 -0400 [thread overview]
Message-ID: <4F80A3AF.2070406@gmail.com> (raw)
In-Reply-To: <201204061711.q36HBpAh015060@lab-41.internal.tilera.com>
Chris Metcalf wrote:
> Commit 026cee0086f had the side-effect of dropping the '=' from
> the unknown boot arguments that are passed to init as environment
> variables. This is because parse_args() puts a NUL in the string
> where the '=' was when it passes the "param" and "val" pointers
> to the parsing subfunctions. Previously, unknown_bootoption() was
> the last parse_args() subfunction to run, and it carefully put back
> the '=' character. Now ignore_unknown_bootoption() is the last
> one to run, and it wasn't doing the necessary repair, so the
> envp params ended up with the embedded NUL and were no longer
> seen as valid environment variables by init.
>
> Signed-off-by: Chris Metcalf<cmetcalf@tilera.com>
> ---
> init/main.c | 25 +++++++++++++------------
> 1 files changed, 13 insertions(+), 12 deletions(-)
>
> diff --git a/init/main.c b/init/main.c
> index 9d454f0..44b2433 100644
> --- a/init/main.c
> +++ b/init/main.c
> @@ -225,13 +225,9 @@ static int __init loglevel(char *str)
>
> early_param("loglevel", loglevel);
>
> -/*
> - * Unknown boot options get handed to init, unless they look like
> - * unused parameters (modprobe will find them in /proc/cmdline).
> - */
> -static int __init unknown_bootoption(char *param, char *val)
> +/* Change NUL term back to "=", to make "param" the whole string. */
> +static int __init repair_env_string(char *param, char *val)
> {
> - /* Change NUL term back to "=", to make "param" the whole string. */
> if (val) {
> /* param=val or param="val"? */
> if (val == param+strlen(param)+1)
> @@ -243,6 +239,16 @@ static int __init unknown_bootoption(char *param, char *val)
> } else
> BUG();
> }
> + return 0;
> +}
> +
> +/*
> + * Unknown boot options get handed to init, unless they look like
> + * unused parameters (modprobe will find them in /proc/cmdline).
> + */
> +static int __init unknown_bootoption(char *param, char *val)
> +{
> + repair_env_string(param, val);
>
> /* Handle obsolete-style parameters */
> if (obsolete_checksetup(param))
> @@ -732,11 +738,6 @@ static char *initcall_level_names[] __initdata = {
> "late parameters",
> };
>
> -static int __init ignore_unknown_bootoption(char *param, char *val)
> -{
> - return 0;
> -}
> -
> static void __init do_initcall_level(int level)
> {
> extern const struct kernel_param __start___param[], __stop___param[];
> @@ -747,7 +748,7 @@ static void __init do_initcall_level(int level)
> static_command_line, __start___param,
> __stop___param - __start___param,
> level, level,
> - ignore_unknown_bootoption);
> + repair_env_string);
>
> for (fn = initcall_levels[level]; fn< initcall_levels[level+1]; fn++)
> do_one_initcall(*fn);
Thanks for the patch, works for me...
Woody
next prev parent reply other threads:[~2012-04-07 20:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-06 16:53 [PATCH] init: fix bug where environment vars can't be passed via boot args Chris Metcalf
2012-04-07 20:29 ` Woody Suwalski [this message]
2012-04-10 13:15 ` Pawel Moll
2012-04-19 22:17 ` Andrew Morton
2012-04-20 13:41 ` Chris Metcalf
2012-04-26 19:54 ` Chris Metcalf
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=4F80A3AF.2070406@gmail.com \
--to=terraluna977@gmail.com \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=cmetcalf@tilera.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=pawel.moll@arm.com \
--cc=rusty@rustcorp.com.au \
--cc=sgruszka@redhat.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