From: Petr Mladek <pmladek@suse.com>
To: John Ogness <john.ogness@linutronix.de>
Cc: Sergey Senozhatsky <senozhatsky@chromium.org>,
Steven Rostedt <rostedt@goodmis.org>,
Marcos Paulo de Souza <mpdesouza@suse.com>,
Chris Down <chris@chrisdown.name>,
Naveen Kumar Chaudhary <naveen.osdev@gmail.com>,
printk@lists.linux.dev, linux-kernel@vger.kernel.org,
Petr Mladek <pmladek@suse.com>
Subject: [PATCH v6 05/16] printk: Do not accept an empty name or devname as a preferred console
Date: Fri, 6 Nov 2026 18:19:41 +0100 [thread overview]
Message-ID: <20261106171952.207909-6-pmladek@suse.com> (raw)
In-Reply-To: <20261106171952.207909-1-pmladek@suse.com>
The current code for storing preferred consoles does not expect
the case when an empty string is passed via @name or @devname.
Empty console driver name does not make any sense. Avoid handling
such entries completely.
Suggested-by: Chris Down <chris@chrisdown.name>
Reviewed-by: Petr Mladek <pmladek@suse.com>
---
kernel/printk/printk.c | 9 ++++++++-
1 file changed, 8 insertions(+), 1 deletion(-)
diff --git a/kernel/printk/printk.c b/kernel/printk/printk.c
index b7543fea865b..6bba67e142e1 100644
--- a/kernel/printk/printk.c
+++ b/kernel/printk/printk.c
@@ -2558,7 +2558,9 @@ asmlinkage __visible void early_printk(const char *fmt, ...)
*
* The function adds or updates an entry in preferred_consoles[] array. Also
* it updates some global variables which are used to make the right decisions
- * in register_console().
+ * in register_console(). Finally, it enforces some rules:
+ *
+ * 1. Do not accept empty @name or @devname.
*/
static int add_or_update_preferred_console(unsigned int i,
const char *name, const short idx,
@@ -2576,6 +2578,11 @@ static int add_or_update_preferred_console(unsigned int i,
if (!name && !devname)
return -EINVAL;
+ if ((name && !name[0]) || (devname && !devname[0])) {
+ pr_err("Adding a preferred console with an empty name\n");
+ return -EINVAL;
+ }
+
/*
* We use a signed short index for struct console for device drivers to
* indicate a not yet assigned index or port. However, a negative index
--
2.56.0
next prev parent reply other threads:[~2026-11-06 17:21 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-06 17:19 [PATCH v6 00/16] printk: Clean up preferred console handling Petr Mladek
2026-11-06 17:19 ` [PATCH v6 01/16] printk: Rename struct console_cmdline to preferred_console Petr Mladek
2026-11-06 17:19 ` [PATCH v6 02/16] printk: Rename preferred_console to preferred_dev_console Petr Mladek
2026-11-06 17:19 ` [PATCH v6 03/16] printk: Cleanup _braille_(un)register_console() wrappers Petr Mladek
2026-11-06 17:19 ` [PATCH v6 04/16] printk: Separate code for adding/updating preferred console metadata Petr Mladek
2026-11-06 17:19 ` Petr Mladek [this message]
2026-11-06 17:19 ` [PATCH v6 06/16] printk: Prefer the console either via name or devname exclusively Petr Mladek
2026-11-06 17:19 ` [PATCH v6 07/16] printk: Check that index is not defined when a console is preferred via devname Petr Mladek
2026-11-06 17:19 ` [PATCH v6 08/16] printk: Ensure consistent name and devname when updating preferred console Petr Mladek
2026-11-06 17:19 ` [PATCH v6 09/16] printk: Do not quietly ignore adding entry for a preferred console when there is no space Petr Mladek
2026-11-06 17:19 ` [PATCH v6 10/16] printk: Allow to debug misuse of add_or_update_preferred_console() Petr Mladek
2026-11-06 17:19 ` [PATCH v6 11/16] console/braille: Lock console->setup() call during the registration Petr Mladek
2026-11-06 17:19 ` [PATCH v6 12/16] printk: Separate code for enabling console Petr Mladek
2026-11-06 17:19 ` [PATCH v6 13/16] printk: Try to register each console as Braille first Petr Mladek
2026-11-06 17:19 ` [PATCH v6 14/16] printk: Do not set Braille console as preferred_console Petr Mladek
2026-11-06 17:19 ` [PATCH v6 15/16] printk: Modify try_enable_default_console() to return error/success Petr Mladek
2026-11-06 17:19 ` [PATCH v6 16/16] printk: Try enable preferred consoles only when there are any 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=20261106171952.207909-6-pmladek@suse.com \
--to=pmladek@suse.com \
--cc=chris@chrisdown.name \
--cc=john.ogness@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mpdesouza@suse.com \
--cc=naveen.osdev@gmail.com \
--cc=printk@lists.linux.dev \
--cc=rostedt@goodmis.org \
--cc=senozhatsky@chromium.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
all inboxes | Powered by JetHome®