From: John Ogness <john.ogness@linutronix.de>
To: Petr Mladek <pmladek@suse.com>
Cc: Sergey Senozhatsky <senozhatsky@chromium.org>,
Steven Rostedt <rostedt@goodmis.org>,
Ryan Roberts <ryan.roberts@arm.com>,
Breno Leitao <leitao@debian.org>,
printk@lists.linux.dev, linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Rio <rioo.tsukatsukii@gmail.com>,
Danilo Krummrich <dakr@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Bradley Morgan <brads@mainlining.org>,
Pnina Feder <pnina.feder@mobileye.com>,
Alessandro Carminati <acarmina@redhat.com>,
Gal Pressman <gal@nvidia.com>, Baoquan He <baoquan.he@linux.dev>,
Mike Rapoport <rppt@kernel.org>,
Pasha Tatashin <pasha.tatashin@soleen.com>,
Pratyush Yadav <pratyush@kernel.org>,
Dave Young <ruirui.yang@linux.dev>,
Pavel Tikhomirov <ptikhomirov@virtuozzo.com>,
Oleg Nesterov <oleg@redhat.com>,
Bradley Morgan <include@grrlz.net>,
Alex Elder <elder@riscstar.com>,
"Cen Zhang (Microsoft)" <blbllhy@gmail.com>,
Petr Pavlu <petr.pavlu@suse.com>,
kexec@lists.infradead.org,
Gustavo Luiz Duarte <gustavold@gmail.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@kernel.org>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
netdev@vger.kernel.org
Subject: [PATCH printk v4 0/8] Introduce policies for unsafe flushing
Date: Sat, 21 Nov 2026 17:41:48 +0106 [thread overview]
Message-ID: <20261121163557.963029-1-john.ogness@linutronix.de> (raw)
v3 is here [0].
Until now unsafe flushing is only performed at the very end of
panic(), before entering the infinite loop. For other situations
(such as panic-kexec or panic-reboot or emergency-reboot) no
unsafe flushing is performed. The reasoning for this is because
an unsafe flush could lead to fireworks, which could prevent the
kexec or reboot from occurring.
However, some users may be willing to take on such risks in order
to see panic output. Indeed, for the netconsole (which does not
support safe atomic printing) it is a regression that such unsafe
printing does not occur. [1]
This series adds unsafe flushing policy flags per-console to
allow individual consoles to perform unsafe flushing for such
scenarios. The unsafe flushing is hard-code-enabled for the
netconsole in patch 8/8. The justification is that this is not
less safe than the legacy netconsole.
Later these policy flags could be easily exposed to userspace
via /sys/class/consoles/, once the sysfs per-console interface
is available.
The first 5 patches have no functional changes.
Changes since v3:
- Restore WARN for non-panic hostile takeover attempts and
expand the comment so I don't attempt this again.
- Rename nbcon_allow_unsafe_takeover() to nbcon_allow_unsafe()
because it now allows general unsafe usage and not
specifically hostile takeovers.
- In __nbcon_atomic_flush_pending(), additionally use
panic_on_this_cpu() to determine if a hostile takeover is
allowed.
John Ogness
[0] https://lore.kernel.org/lkml/20261118230345.808560-1-john.ogness@linutronix.de
[1] https://lore.kernel.org/lkml/20260915100140.3631650-1-ryan.roberts@arm.com
John Ogness (8):
printk: Introduce and specify flush reasons
printk: nbcon: Move unsafe takeover check to higher level
printk: Move unsafe takeover check out of console_is_usable()
printk: nbcon: Use @reason instead of global variable to check flush
policy
printk: nbcon: Expand unsafe takeover check for general unsafe
console: Support unsafe flushing for panic/emergency restarts
printk: Add unsafe flush points for panic+kexec and emergency_restart
netconsole: Perform unsafe flushing on panic and emergency restart
drivers/net/netconsole.c | 2 +
include/linux/console.h | 60 +++++++++++++++++-----
include/linux/printk.h | 20 +++++++-
kernel/crash_core.c | 1 +
kernel/panic.c | 2 +-
kernel/printk/nbcon.c | 105 ++++++++++++++++++++++++++++-----------
kernel/reboot.c | 1 +
7 files changed, 147 insertions(+), 44 deletions(-)
base-commit: 52904cd86a5f8c83fd956d1b2b9cd12593597e7b
--
2.47.3
next reply other threads:[~2026-11-21 16:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-21 16:35 John Ogness [this message]
2026-11-21 16:35 ` [PATCH printk v4 1/8] printk: Introduce and specify flush reasons John Ogness
2026-11-21 16:35 ` [PATCH printk v4 2/8] printk: nbcon: Move unsafe takeover check to higher level John Ogness
2026-11-21 16:35 ` [PATCH printk v4 3/8] printk: Move unsafe takeover check out of console_is_usable() John Ogness
2026-11-21 16:35 ` [PATCH printk v4 4/8] printk: nbcon: Use @reason instead of global variable to check flush policy John Ogness
2026-11-21 16:35 ` [PATCH printk v4 5/8] printk: nbcon: Expand unsafe takeover check for general unsafe John Ogness
2026-11-21 16:35 ` [PATCH printk v4 6/8] console: Support unsafe flushing for panic/emergency restarts John Ogness
2026-11-21 16:35 ` [PATCH printk v4 7/8] printk: Add unsafe flush points for panic+kexec and emergency_restart John Ogness
2026-11-21 16:35 ` [PATCH printk v4 8/8] netconsole: Perform unsafe flushing on panic and emergency restart John Ogness
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=20261121163557.963029-1-john.ogness@linutronix.de \
--to=john.ogness@linutronix.de \
--cc=acarmina@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=andrew+netdev@lunn.ch \
--cc=baoquan.he@linux.dev \
--cc=blbllhy@gmail.com \
--cc=brads@mainlining.org \
--cc=dakr@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=elder@riscstar.com \
--cc=gal@nvidia.com \
--cc=gregkh@linuxfoundation.org \
--cc=gustavold@gmail.com \
--cc=include@grrlz.net \
--cc=kexec@lists.infradead.org \
--cc=kuba@kernel.org \
--cc=leitao@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=pabeni@redhat.com \
--cc=pasha.tatashin@soleen.com \
--cc=petr.pavlu@suse.com \
--cc=pmladek@suse.com \
--cc=pnina.feder@mobileye.com \
--cc=pratyush@kernel.org \
--cc=printk@lists.linux.dev \
--cc=ptikhomirov@virtuozzo.com \
--cc=rioo.tsukatsukii@gmail.com \
--cc=rostedt@goodmis.org \
--cc=rppt@kernel.org \
--cc=ruirui.yang@linux.dev \
--cc=ryan.roberts@arm.com \
--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®