| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-Id: <20200430161438.17640-4-alpernebiyasak@gmail.com>
Date: Thu, 30 Apr 2020 19:14:37 +0300
From: Alper Nebi Yasak <alpernebiyasak@...il.com>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Jiri Slaby <jslaby@...e.com>, Petr Mladek <pmladek@...e.com>,
Sergey Senozhatsky <sergey.senozhatsky@...il.com>
Cc: linux-serial@...r.kernel.org, Steven Rostedt <rostedt@...dmis.org>,
Alper Nebi Yasak <alpernebiyasak@...il.com>,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: [RFC PATCH v2 3/3] printk: Preset tty0 as a pseudo-preferred console
The ACPI SPCR (Serial Port Console Redirection) table from a machine's
firmware can specify a serial console which can be used for earlycon.
However, in at least ARM64 systems the same device is also set up as the
preferred console. Presumably due to the order of acpi_parse_spcr and
VT's register_device calls, setting the specified console as the
preferred one can prevent registering VT as a console.
This might look appropriate for machines which do not have or need
working graphics and whose users most likely have access to a serial
port. However, the use of SPCR tables may not be limited these. For
example, ARM64 QEMU virtual machines include a SPCR table regardless of
the existence of a graphics output or even the nonexistence of a serial
console. Or server hardware which has a SPCR table can be repurposed
into a workstation with the addition of a graphics card. As a result,
boot messages and early userspace prompts can go to an unexpected
console.
This patch presets tty0 as a pseudo-preferred console at compile-time to
ensure that CONFIG_VT_CONSOLE always results in the VT console getting
registered. With this, VT can get registered, these other consoles are
preferred when VT is a dummy, but we can also bump up VTs preference
when working graphics are available.
Without this patch, an ARM64 QEMU virtual machine has roughly the
following order of console events and consoles:
# Without earlycon:
$ sudo dmesg | grep -i "console\|printk\|tty[0-9a-z]" | grep -v systemd
[ 0.000000] ACPI: SPCR: console: pl011,mmio,0x9000000,9600
[ 0.000250] Console: colour dummy device 80x25
[ 0.140955] ARMH0011:00: ttyAMA0 at MMIO 0x9000000 (irq = 4, base_baud = 0) is a SBSA
[ 0.317189] printk: console [ttyAMA0] enabled
[ 3.540272] Console: switching to colour frame buffer device 150x42
$ cat /proc/consoles
ttyAMA0 -W- (EC p a) 204:64
# With earlycon:
$ sudo dmesg | grep -i "console\|printk\|tty[0-9a-z]" | grep -v systemd
[ 0.000000] ACPI: SPCR: console: pl011,mmio,0x9000000,9600
[ 0.000000] printk: bootconsole [pl11] enabled
[ 0.002064] Console: colour dummy device 80x25
[ 0.324415] ARMH0011:00: ttyAMA0 at MMIO 0x9000000 (irq = 4, base_baud = 0) is a SBSA
[ 0.327047] printk: console [ttyAMA0] enabled
[ 0.329139] printk: bootconsole [pl11] disabled
[ 3.704937] Console: switching to colour frame buffer device 150x42
$ cat /proc/consoles
ttyAMA0 -W- (EC a) 204:64
In addition, boot messages aren't printed to the framebuffer (as tty0 is
not registered). With this patch, boot messages are visible on the
framebuffer and the information above becomes:
# Without earlycon:
$ sudo dmesg | grep -i "console\|printk\|tty[0-9a-z]" | grep -v systemd
[ 0.000000] ACPI: SPCR: console: pl011,mmio,0x9000000,9600
[ 0.000058] Console: colour dummy device 80x25
[ 0.000266] printk: console [tty0] enabled
[ 0.144615] ARMH0011:00: ttyAMA0 at MMIO 0x9000000 (irq = 4, base_baud = 0) is a SBSA
[ 0.299031] printk: console [ttyAMA0] enabled
[ 3.320333] Console: switching to colour frame buffer device 150x42
[ 3.329386] printk: switching to console [tty0]
$ cat /proc/consoles
tty0 -WU (EC p ) 4:7
ttyAMA0 -W- (E p a) 204:64
# With earlycon:
$ sudo dmesg | grep -i "console\|printk\|tty[0-9a-z]" | grep -v systemd
[ 0.000000] ACPI: SPCR: console: pl011,mmio,0x9000000,9600
[ 0.000000] printk: bootconsole [pl11] enabled
[ 0.002326] Console: colour dummy device 80x25
[ 0.003545] printk: console [tty0] enabled
[ 0.236824] ARMH0011:00: ttyAMA0 at MMIO 0x9000000 (irq = 4, base_baud = 0) is a SBSA
[ 0.239243] printk: console [ttyAMA0] enabled
[ 0.241324] printk: bootconsole [pl11] disabled
[ 3.715086] Console: switching to colour frame buffer device 150x42
[ 3.742923] printk: switching to console [tty0]
$ cat /proc/consoles
tty0 -WU (EC p ) 4:7
ttyAMA0 -W- (E a) 204:64
Signed-off-by: Alper Nebi Yasak <alpernebiyasak@...il.com>
---
Changes in v2:
- Fix #elif to #else (Reported-by: kbuild test robot <lkp@...el.com>)
- Refresh dmesg outputs with/without earlycon for next-20200430
kernel/printk/printk.c | 12 ++++++++++++
1 file changed, 12 insertions(+)
diff --git a/kernel/printk/printk.c b/kernel/printk/printk.c
index efda422203e4..aa9f9f16860f 100644
--- a/kernel/printk/printk.c
+++ b/kernel/printk/printk.c
@@ -277,7 +277,19 @@ static struct console *exclusive_console;
#define MAX_CMDLINECONSOLES 8
+/*
+ * The preferred_console and has_preferred_console variables are
+ * intentionally not modified to reflect this so that the first
+ * registered console is still used as the preferred console.
+ */
+#ifdef CONFIG_VT_CONSOLE
+static struct console_cmdline console_cmdline[MAX_CMDLINECONSOLES] = {
+ [0].name = "tty",
+ [0].index = 0,
+};
+#else
static struct console_cmdline console_cmdline[MAX_CMDLINECONSOLES];
+#endif
static int preferred_console = -1;
static bool has_preferred_console;
--
2.26.2
Powered by blists - more mailing lists