From: Steven Rostedt <rostedt@goodmis.org>
To: Masami Hiramatsu <mhiramat@kernel.org>
Cc: Arvind Sankar <nivedita@alum.mit.edu>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] bootconfig: Fix to find the initargs correctly
Date: Tue, 4 Aug 2020 16:59:29 -0400 [thread overview]
Message-ID: <20200804165929.3bfeb318@oasis.local.home> (raw)
In-Reply-To: <159650953285.270383.14822353843556363851.stgit@devnote2>
On Tue, 4 Aug 2020 11:52:13 +0900
Masami Hiramatsu <mhiramat@kernel.org> wrote:
> Since the parse_args() stops parsing at '--', bootconfig_params()
> will never get the '--' as param and initargs_found never be true.
> In the result, if we pass some init arguments via the bootconfig,
> those are always appended to the kernel command line with '--'
> even if the kernel command line already has '--'.
>
> To fix this correctly, check the return value of parse_args()
> and set initargs_found true if the return value is not an error
> but a valid address.
Thanks Masami,
I'll start testing this now. I just finished testing everything else I
had in my queue and pushed it to my for-next branch. Can you check to
see if I missed anything there?
-- Steve
>
> Fixes: f61872bb58a1 ("bootconfig: Use parse_args() to find bootconfig and '--'")
> Cc: stable@vger.kernel.org
> Reported-by: Arvind Sankar <nivedita@alum.mit.edu>
> Suggested-by: Arvind Sankar <nivedita@alum.mit.edu>
> Signed-off-by: Masami Hiramatsu <mhiramat@kernel.org>
> ---
> Changes in v2:
> - Remvoe unneede !IS_ERR().
> ---
> init/main.c | 14 ++++++++------
> 1 file changed, 8 insertions(+), 6 deletions(-)
>
> diff --git a/init/main.c b/init/main.c
> index 0ead83e86b5a..883ded3638e5 100644
> --- a/init/main.c
> +++ b/init/main.c
> @@ -387,8 +387,6 @@ static int __init bootconfig_params(char *param, char *val,
> {
> if (strcmp(param, "bootconfig") == 0) {
> bootconfig_found = true;
> - } else if (strcmp(param, "--") == 0) {
> - initargs_found = true;
> }
> return 0;
> }
> @@ -399,19 +397,23 @@ static void __init setup_boot_config(const char *cmdline)
> const char *msg;
> int pos;
> u32 size, csum;
> - char *data, *copy;
> + char *data, *copy, *err;
> int ret;
>
> /* Cut out the bootconfig data even if we have no bootconfig option */
> data = get_boot_config_from_initrd(&size, &csum);
>
> strlcpy(tmp_cmdline, boot_command_line, COMMAND_LINE_SIZE);
> - parse_args("bootconfig", tmp_cmdline, NULL, 0, 0, 0, NULL,
> - bootconfig_params);
> + err = parse_args("bootconfig", tmp_cmdline, NULL, 0, 0, 0, NULL,
> + bootconfig_params);
>
> - if (!bootconfig_found)
> + if (IS_ERR(err) || !bootconfig_found)
> return;
>
> + /* parse_args() stops at '--' and returns an address */
> + if (err)
> + initargs_found = true;
> +
> if (!data) {
> pr_err("'bootconfig' found on command line, but no bootconfig found\n");
> return;
next prev parent reply other threads:[~2020-08-04 20:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-04 2:52 Masami Hiramatsu
2020-08-04 20:59 ` Steven Rostedt [this message]
2020-08-05 7:41 ` Masami Hiramatsu
-- strict thread matches above, loose matches on Subject: below --
2020-08-04 2:51 Masami Hiramatsu
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=20200804165929.3bfeb318@oasis.local.home \
--to=rostedt@goodmis.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=nivedita@alum.mit.edu \
/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
all inboxes | Powered by JetHome®