From: Petr Mladek <pmladek@suse.com>
To: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Cc: Guenter Roeck <linux@roeck-us.net>,
Shreyas Joshi <shreyas.joshi@biamp.com>,
rostedt@goodmis.org, shreyasjoshi15@gmail.com,
linux-kernel@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH] printk: handle blank console arguments passed in.
Date: Wed, 7 Oct 2020 09:28:53 +0200 [thread overview]
Message-ID: <20201007072853.GF32369@alley> (raw)
In-Reply-To: <20201006171504.GA64770@jagdpanzerIV.localdomain>
On Wed 2020-10-07 02:15:04, Sergey Senozhatsky wrote:
> On (20/10/06 18:35), Petr Mladek wrote:
> > > > Whatever is decided, I'd like to have it made official and documented to
> > > > avoid a similar problem in the future.
> >
> > Sigh, it is even bigger mess than I expected. There is a magic
> > variable "console_set_on_cmdline". It used, for example, in
> > of_console_check() to prevent using the default console from dts.
>
> I wonder if we can do something like:
>
> ---
> @@ -2200,6 +2200,9 @@ static int __init console_setup(char *str)
> char *s, *options, *brl_options = NULL;
> int idx;
>
> if (str[0] == 0) {
> + console_set_on_cmdline = 1;
Unfortunately, this is not enough. We will also need to prevent
enabling the fallback console when has_preferred_console is not set.
The following might work:
/*
* Dirty hack to prevent using any console with tty
* binding as a fallback and adding the empty
* name into console_cmdline array.
*/
preferred_console = MAX_CMDLINECONSOLES;
> return 1;
> }
It might be the minimal change that would fix the regression and keep
the original fix. But it would make the code even more hairy.
It might be acceptable as a hotfix. But we really should somehow clean
up the code and try to make the behavior more consistent.
Best Regards,
Petr
next prev parent reply other threads:[~2020-10-07 7:28 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-09 5:29 [PATCH] printk: handle blank console arguments passed in Shreyas Joshi
2020-03-17 1:34 ` Shreyas Joshi
2020-03-17 1:39 ` Steven Rostedt
2020-03-17 2:01 ` Sergey Senozhatsky
2020-03-17 2:17 ` Shreyas Joshi
2020-03-17 8:22 ` Sergey Senozhatsky
2020-05-22 6:46 ` Shreyas Joshi
2020-05-22 6:53 ` Shreyas Joshi
2020-05-22 10:00 ` Petr Mladek
2020-10-06 2:59 ` Sergey Senozhatsky
2020-10-06 3:35 ` Guenter Roeck
2020-10-06 5:08 ` Greg Kroah-Hartman
2020-10-06 11:17 ` Guenter Roeck
2020-10-06 6:59 ` Sergey Senozhatsky
2020-10-06 9:54 ` Petr Mladek
2020-10-06 13:33 ` Sergey Senozhatsky
2020-10-06 14:22 ` Guenter Roeck
2020-10-06 16:08 ` Sergey Senozhatsky
2020-10-06 9:52 ` Petr Mladek
2020-10-06 10:45 ` Guenter Roeck
2020-10-06 13:43 ` Petr Mladek
2020-10-06 16:35 ` Petr Mladek
2020-10-06 17:15 ` Sergey Senozhatsky
2020-10-07 7:28 ` Petr Mladek [this message]
2020-10-07 12:30 ` Sergey Senozhatsky
2020-10-07 14:39 ` Sergey Senozhatsky
2020-10-07 15:57 ` Guenter Roeck
2020-10-07 16:29 ` Sergey Senozhatsky
2020-10-08 5:52 ` Sergey Senozhatsky
2020-10-08 9:01 ` Petr Mladek
2020-10-08 10:56 ` Sergey Senozhatsky
2020-10-08 12:05 ` Sergey Senozhatsky
2020-10-22 11:38 ` Petr Mladek
2020-10-22 13:32 ` Sergey Senozhatsky
2020-10-08 8:50 ` Petr Mladek
2020-10-08 12:20 ` Sergey Senozhatsky
2020-10-08 12:37 ` Sergey Senozhatsky
2020-05-15 15:24 ` Petr Mladek
2020-05-20 11:50 ` Sergey Senozhatsky
2020-05-22 6:40 ` Shreyas Joshi
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=20201007072853.GF32369@alley \
--to=pmladek@suse.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=rostedt@goodmis.org \
--cc=sergey.senozhatsky@gmail.com \
--cc=shreyas.joshi@biamp.com \
--cc=shreyasjoshi15@gmail.com \
--cc=torvalds@linux-foundation.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