If a console was specified by ACPI SPCR table _and_ command line parameters like
"console=ttyAMA0" _and_ "earlycon" were specified, then log messages
appear twice.
This issue was addressed in the patch [1] but the approach was wrong and
a revert [2] was suggested.
First two patches "printk: fix name/type/scope of preferred_console var" and
"printk: rename selected_console -> preferred_console" were sent some
time ago as one patch "printk: fix name and type of some variables" [3].
They fix name/type/scope of some variables without changing the logic.
The real fix is in the second patch. The root cause is that the code traverses
the list of specified consoles (the `console_cmdline` array) and stops at the
first match. But it may happen that the same console is referred by
the elements of this array twice:
pl011,mmio,0x87e024000000,115200 -- from SPCR
ttyAMA0 -- from command line
but in this case `preferred_console` points to the second entry and
the flag CON_CONSDEV is not set, so bootconsole is not deregistered.
To fix that, introduce an invariant "The last non-braille console is always the
preferred one" on the entries of the console_cmdline array and don't try to
check for double entries. Then traverse it in reverse order to be sure that if
the console is preferred then it will be the first matching entry.
v5:
- rewrite 3/3. Insetead of rearranging the loop, introduce an invariant
"The last non-braille console is always the preferred one" on the
entries of the console_cmdline array and don't try to check for double
entries. Then traverse it in reverse order to be sure that if the console
is preferred then it will be the first matching entry.
- add a better explanation from Petr Mladek for 2/3.
v4:
It was not sent upstream due to some problems in implementation of 3/3.
- add some Acked-by: and Reviewed-by: to 1/3 and 2/3
- v2 was closer to the original logic, even though v3 looked simpler.
The problem is that newcon->setup() is called twice, firstly
from newcon->match(), then explicitly. And it could be called third time
later in another call to newcon->match(). Implement correct sequence:
1) try to match against preferred_console,
2) if that fails check other entries of console_cmdline.
Also move braille console matching/registration to a separate pass to simplify
the code.
v3 (only for 3/3):
https://lkml.kernel.org/r/20170303154946.15399-1-aleksey.maka...@linaro.org
- v2 still changes the logic of the code and calls newcon->match() several
times. V3 fixes that. It initially matches the console against
the preferred_console entry, and then if that fails, against other entries.
v2:
https://lkml.kernel.org/r/20170302131153.22733-1-aleksey.maka...@linaro.org
- split the patch that renames `selected_console` and `preferred_console`
into two patches (Steven Rostedt)
- add a comment explaining why we need a separate match to check for
preferred_console (Steven Rostedt)
- v1 of this patchset changed the logic of console initialization a bit.
That could lead to bugs/incompatibilities. Use the exactly the same
logic as in the original code.
v1:
https://lkml.kernel.org/r/20170301161347.4202-1-aleksey.maka...@linaro.org
[1]
https://lkml.kernel.org/r/1485963998-921-1-git-send-email-sudeep.ho...@arm.com
commit aea9a80ba98a ("tty: serial: pl011: add ttyAMA for matching pl011
console")
[2] https://lkml.kernel.org/r/20170301152304.29635-1-aleksey.maka...@linaro.org
[3]
https://lkml.kernel.org/r/1455299022-11641-2-git-send-email-aleksey.maka...@linaro.org
Aleksey Makarov (3):
printk: fix name/type/scope of preferred_console var
printk: rename selected_console -> preferred_console
printk: fix double printing with earlycon
kernel/printk/printk.c | 61 ++++++++++++++++++++++++++++++--------------------
1 file changed, 37 insertions(+), 24 deletions(-)
--
2.12.0
