stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jason Baron <jbaron@akamai.com>
To: Peter Chen <peter.chen@freescale.com>
Cc: corbet@lwn.net, linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH 1/2] dynamic_debug: fix boot parameters parse
Date: Wed, 28 Oct 2015 10:17:59 -0400	[thread overview]
Message-ID: <5630D917.7010607@akamai.com> (raw)
In-Reply-To: <1445931626-11158-1-git-send-email-peter.chen@freescale.com>

On 10/27/2015 03:40 AM, Peter Chen wrote:
> The parse_args will delete space between boot parameters, so
> if we add dyndbg="file drivers/usb/* +p" at bootargs, the parse_args
> will split it as three parameters, and only "file" is for dyndbg,
> then below error will occur at ddebug, it causes all non-module
> ddebug fail during the boot process.
> 
> ===============================================================
> dynamic_debug:ddebug_parse_flags: bad flag-op f, at start of file
> dynamic_debug:ddebug_exec_query: flags parse failed
> ===============================================================
> 

Hi,

So the spaces there should be preserved if they are in quotes. Looking at
kernel/params.c:next_arg(), the comment there explicitly says:

/* You can use " around spaces, but can't escape ". */

So this should still be working. And if its not, I suspect other
command-line parsing would be broken as well. So if it did change,
what changed in command line parsing?

What's the output of $ cat /proc/cmdline ? Perhaps, the quotes
were not passed properly from the bootloader to the kernel?

Thanks,

-Jason


> As a solution, we can use comma to split parameters for ddebug booting
> parameter, and replace comma with space at code, in that case, the ddebug
> core can handle it with the same way we do it for /sys.
> 
> Signed-off-by: Peter Chen <peter.chen@freescale.com>
> Cc: <stable@vger.kernel.org>
> ---
>  lib/dynamic_debug.c | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/lib/dynamic_debug.c b/lib/dynamic_debug.c
> index e491e02..da4883b 100644
> --- a/lib/dynamic_debug.c
> +++ b/lib/dynamic_debug.c
> @@ -880,6 +880,8 @@ static int ddebug_dyndbg_param_cb(char *param, char *val,
>  	if (strcmp(param, "dyndbg"))
>  		return on_err; /* determined by caller */
>  
> +	/* relace comma with space */
> +	strreplace(val, ',', ' ');
>  	ddebug_exec_queries((val ? val : "+p"), modname);
>  
>  	return 0; /* query failure shouldnt stop module load */
> 


  parent reply	other threads:[~2015-10-28 14:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-27  7:40 [PATCH 1/2] dynamic_debug: fix boot parameters parse Peter Chen
2015-10-27  7:40 ` [PATCH 2/2] Doc: dynamic-debug-howto: fix the way to enable ddebug during boot process Peter Chen
2015-10-28 14:17 ` Jason Baron [this message]
2015-10-29  6:22   ` [PATCH 1/2] dynamic_debug: fix boot parameters parse Peter Chen

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=5630D917.7010607@akamai.com \
    --to=jbaron@akamai.com \
    --cc=corbet@lwn.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peter.chen@freescale.com \
    --cc=stable@vger.kernel.org \
    /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).