From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Petr Mladek <pmladek@suse.com>
Cc: linux-kernel@vger.kernel.org,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
Steven Rostedt <rostedt@goodmis.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
AlekseyMakarov <aleksey.makarov@linaro.org>
Subject: Re: [RFC/PATCH] printk: Fix preferred console selection with multiple matches
Date: Mon, 16 Dec 2019 11:09:33 +1100 [thread overview]
Message-ID: <0511b917d8ebcf594480349b79fcb9f14aa882f9.camel@kernel.crashing.org> (raw)
In-Reply-To: <20191211091740.p6bgjy7sy75maenw@pathway.suse.cz>
On Wed, 2019-12-11 at 10:17 +0100, Petr Mladek wrote:
> The reverse search of list of console does not work for ttySX
> consoles because the number is omitted when matching. And the messages
> will appear only on the first matched serial console. There is
> a paragraph about this in the commit message of my patch.
About that specific issue...
I see indeed that 8250_core.c registers a "generic" console with index
-1 which will match whetever we hit first in the array.
This is actually wrong isn't it ? Without any change such as what we've
been proposing, it means that an arch doing add_preferred_console of
any ttyS* will override anything on the command line, and it also means
that a command line with multiple ttyS entries will stop at the first
one, not the last one.
IE. In both case the code will select a console that isn't
preferred_console... or am I missing something subtle ?
So yes, fixing that will "regress" in the sense that it will change the
behaviour, but to make it match what's documented... am I wrong ?
The question then becomes what's the most broken ? Changing the
behaviour that might have become expected or leaving the (alledgedly)
broken behaviour in place ?
Cheers,
Ben.
next prev parent reply other threads:[~2019-12-16 0:10 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-10 0:57 Benjamin Herrenschmidt
2019-12-10 8:01 ` Sergey Senozhatsky
2019-12-10 22:26 ` Benjamin Herrenschmidt
2019-12-11 2:01 ` Sergey Senozhatsky
2019-12-11 4:02 ` Benjamin Herrenschmidt
2019-12-11 5:35 ` Sergey Senozhatsky
2019-12-11 12:53 ` Petr Mladek
2019-12-10 9:15 ` Petr Mladek
2019-12-10 22:39 ` Benjamin Herrenschmidt
2019-12-11 9:17 ` Petr Mladek
2019-12-12 1:23 ` Sergey Senozhatsky
2019-12-16 0:09 ` Benjamin Herrenschmidt [this message]
2019-12-19 9:50 ` Petr Mladek
2019-12-12 0:35 ` Benjamin Herrenschmidt
2019-12-12 9:09 ` Petr Mladek
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=0511b917d8ebcf594480349b79fcb9f14aa882f9.camel@kernel.crashing.org \
--to=benh@kernel.crashing.org \
--cc=aleksey.makarov@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=sergey.senozhatsky@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
Powered by JetHome