From: Breno Leitao <leitao@debian.org>
To: Breno Leitao <leitao@debian.org>,
Jakub Kicinski <kuba@kernel.org>,
horms@kernel.org, efault@gmx.de, john.ogness@linutronix.de,
pmladek@suse.com
Cc: Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
calvin@wbinvd.org, asml.silence@gmail.com, kernel-team@meta.com,
gustavold@gmail.com, asantostc@gmail.com
Subject: [PATCH RFC net-next 2/2] netconsole: add CONFIG_NETCONSOLE_NBCON for nbcon support
Date: Fri, 21 Nov 2025 03:26:08 -0800 [thread overview]
Message-ID: <20251121-nbcon-v1-2-503d17b2b4af@debian.org> (raw)
In-Reply-To: <20251121-nbcon-v1-0-503d17b2b4af@debian.org>
Add optional support for the nbcon infrastructure to netconsole via a new
CONFIG_NETCONSOLE_NBCON compile-time option.
The nbcon infrastructure provides a lock-free, priority-based console
system that supports atomic printing from any context including NMI,
with safe handover mechanisms between different priority levels. This
makes it particularly suitable for crash-safe kernel logging.
When disabled (default), netconsole uses the legacy console callbacks,
maintaining full backward compatibility.
PS: .write_atomic and .write_thread uses the same callback, given that
there is no safe .write_atomic, so .write_atomic is called as the last
resource. This is what CON_NBCON_ATOMIC_UNSAFE is telling nbcon.
Signed-off-by: Breno Leitao <leitao@debian.org>
---
drivers/net/Kconfig | 14 ++++++++++
drivers/net/netconsole.c | 68 ++++++++++++++++++++++++++++++++++++++++++++++++
2 files changed, 82 insertions(+)
diff --git a/drivers/net/Kconfig b/drivers/net/Kconfig
index ac12eaf11755..aa8771b5b723 100644
--- a/drivers/net/Kconfig
+++ b/drivers/net/Kconfig
@@ -369,6 +369,20 @@ config NETCONSOLE_PREPEND_RELEASE
message. See <file:Documentation/networking/netconsole.rst> for
details.
+config NETCONSOLE_NBCON
+ bool "Use nbcon infrastructure (EXPERIMENTAL)"
+ depends on NETCONSOLE
+ default n
+ help
+ Enable nbcon support for netconsole. This uses the new lock-free
+ console infrastructure which supports threaded and atomic printing.
+ Given that netconsole does not support atomic operations, the current
+ implementation focuses on threaded callbacks, unless the host is
+ crashing, then it uses an unsafe atomic callbacks. This feature is
+ available for both extended and non-extended consoles.
+
+ If unsure, say N to use the legacy console infrastructure.
+
config NETPOLL
def_bool NETCONSOLE
diff --git a/drivers/net/netconsole.c b/drivers/net/netconsole.c
index f4b1706fb081..2943f00b83f6 100644
--- a/drivers/net/netconsole.c
+++ b/drivers/net/netconsole.c
@@ -1724,6 +1724,57 @@ static void send_ext_msg_udp(struct netconsole_target *nt, const char *msg,
extradata_len);
}
+#ifdef CONFIG_NETCONSOLE_NBCON
+static void netcon_write_nbcon(struct console *con,
+ struct nbcon_write_context *wctxt,
+ bool extended)
+{
+ struct netconsole_target *nt;
+
+ lockdep_assert_held(&target_list_lock);
+
+ list_for_each_entry(nt, &target_list, list) {
+ if (nt->extended != extended || !nt->enabled ||
+ !netif_running(nt->np.dev))
+ continue;
+
+ if (!nbcon_enter_unsafe(wctxt))
+ continue;
+
+ if (extended)
+ send_ext_msg_udp(nt, wctxt->outbuf, wctxt->len);
+ else
+ write_msg_target(nt, wctxt->outbuf, wctxt->len);
+
+ nbcon_exit_unsafe(wctxt);
+ }
+}
+
+static void netcon_write_nbcon_ext(struct console *con,
+ struct nbcon_write_context *wctxt)
+{
+ netcon_write_nbcon(con, wctxt, true);
+}
+
+static void netcon_write_nbcon_basic(struct console *con,
+ struct nbcon_write_context *wctxt)
+{
+ netcon_write_nbcon(con, wctxt, false);
+}
+
+static void netconsole_device_lock(struct console *con, unsigned long *flags)
+{
+ /* protects all the targets at the same time */
+ spin_lock_irqsave(&target_list_lock, *flags);
+}
+
+static void netconsole_device_unlock(struct console *con, unsigned long flags)
+{
+ spin_unlock_irqrestore(&target_list_lock, flags);
+}
+
+#else
+
static void write_ext_msg(struct console *con, const char *msg,
unsigned int len)
{
@@ -1765,6 +1816,7 @@ static void write_msg(struct console *con, const char *msg, unsigned int len)
}
spin_unlock_irqrestore(&target_list_lock, flags);
}
+#endif
static int netconsole_parser_cmdline(struct netpoll *np, char *opt)
{
@@ -1923,14 +1975,30 @@ static void free_param_target(struct netconsole_target *nt)
static struct console netconsole_ext = {
.name = "netcon_ext",
+#ifdef CONFIG_NETCONSOLE_NBCON
+ .flags = CON_ENABLED | CON_EXTENDED | CON_NBCON | CON_NBCON_ATOMIC_UNSAFE,
+ .write_thread = netcon_write_nbcon_ext,
+ .write_atomic = netcon_write_nbcon_ext,
+ .device_lock = netconsole_device_lock,
+ .device_unlock = netconsole_device_unlock,
+#else
.flags = CON_ENABLED | CON_EXTENDED,
.write = write_ext_msg,
+#endif
};
static struct console netconsole = {
.name = "netcon",
+#ifdef CONFIG_NETCONSOLE_NBCON
+ .flags = CON_ENABLED | CON_NBCON | CON_NBCON_ATOMIC_UNSAFE,
+ .write_thread = netcon_write_nbcon_basic,
+ .write_atomic = netcon_write_nbcon_basic,
+ .device_lock = netconsole_device_lock,
+ .device_unlock = netconsole_device_unlock,
+#else
.flags = CON_ENABLED,
.write = write_msg,
+#endif
};
static int __init init_netconsole(void)
--
2.47.3
next prev parent reply other threads:[~2025-11-21 11:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-21 11:26 [PATCH RFC net-next 0/2] netconsole: NBCON Infrastructure Support Breno Leitao
2025-11-21 11:26 ` [PATCH RFC net-next 1/2] netconsole: extract message fragmentation into write_msg_target() Breno Leitao
2025-11-24 13:08 ` Petr Mladek
2025-11-21 11:26 ` Breno Leitao [this message]
2025-11-24 13:55 ` [PATCH RFC net-next 2/2] netconsole: add CONFIG_NETCONSOLE_NBCON for nbcon support 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=20251121-nbcon-v1-2-503d17b2b4af@debian.org \
--to=leitao@debian.org \
--cc=andrew+netdev@lunn.ch \
--cc=asantostc@gmail.com \
--cc=asml.silence@gmail.com \
--cc=calvin@wbinvd.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=efault@gmx.de \
--cc=gustavold@gmail.com \
--cc=horms@kernel.org \
--cc=john.ogness@linutronix.de \
--cc=kernel-team@meta.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pmladek@suse.com \
/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®