Re: [PATCH] printk: handle blank console arguments passed in.
From: Sergey Senozhatsky
Date: Wed May 20 2020 - 07:50:28 EST
On (20/05/15 17:24), Petr Mladek wrote:
[..]
> > diff --git a/kernel/printk/printk.c b/kernel/printk/printk.c
> > index ad4606234545..e9ad730991e0 100644
> > --- a/kernel/printk/printk.c
> > +++ b/kernel/printk/printk.c
> > @@ -2165,7 +2165,10 @@ static int __init console_setup(char *str)
> > char buf[sizeof(console_cmdline[0].name) + 4]; /* 4 for "ttyS" */
> > char *s, *options, *brl_options = NULL;
> > int idx;
> > -
> > + if (str[0] == 0) {
> > + console_loglevel = 0;
>
> What is the reason to set console_loglevel here, please?
Yeah, doesn't look necessary.
> > + return 1;
> > + }
>
> Anyway, for example, earlycon parameter is allowed to be used with
> empty string when the console parameters can be set via ACPI SPCR,
> see param_setup_earlycon(). Therefore I am afraid that every setup()
> function has to handle this on its own and this patch makes sense.
Hmm, OK.
FWIW,
Acked-by: Sergey Senozhatsky <sergey.senozhatsky@xxxxxxxxx>
-ss