From: Petr Mladek <pmladek@suse.com>
To: Tzung-Bi Shih <tzungbi@kernel.org>
Cc: Kees Cook <kees@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Tony Luck <tony.luck@intel.com>,
"Guilherme G. Piccoli" <gpiccoli@igalia.com>,
Steven Rostedt <rostedt@goodmis.org>,
John Ogness <john.ogness@linutronix.de>,
Sergey Senozhatsky <senozhatsky@chromium.org>,
tfiga@chromium.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] printk: Introduce loglevel bypass for pstore console
Date: Wed, 9 Sep 2026 11:28:33 +0200 [thread overview]
Message-ID: <aqEmwXTLaTyUhhYG@pathway.suse.cz> (raw)
In-Reply-To: <20260831070346.3490745-1-tzungbi@kernel.org>
On Mon 2026-08-31 07:03:44, Tzung-Bi Shih wrote:
> Currently, offline consoles (e.g., pstore_console backed by ramoops)
> inherit the system's global console_loglevel.
>
> In production environments, physical serial consoles (UARTs) are often
> heavily rate-limited to prevent verbose messages from causing severe
> execution bottlenecks. Unfortunately, this identically silences the
> pstore console. When a kernel panic or lockup occurs, engineers are
> left inspecting a crash dump that has been stripped of the verbose logs
> that could have identified the root cause.
>
> This series introduces CON_BYPASS_LOGLEVEL, a simple flag that allows
> specialized offline consoles to request unsuppressed logs directly.
>
> Patch 1 introduces the CON_BYPASS_LOGLEVEL flag.
> Patch 2 adopts the flag in pstore_console.
I believe that a better solution for this problem would be adding
the per-console loglevel feature, see
https://lore.kernel.org/all/cover.1764272407.git.chris@chrisdown.name/
It is currently blocked by a cleanup of the console registration code,
see https://lore.kernel.org/all/20260604101459.393162-1-pmladek@suse.com/
I am going to send v5 of the console registration code cleanup soon,
hopefully later this week or the following week. It would be nice
when it gets some more review.
Best Regards,
Petr
PS: Thanks for reminder. I wanted to answer this mail the same day
when I got it. But I have to interrupted and it somehow fallen
though cracks.
prev parent reply other threads:[~2026-09-09 9:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-31 7:03 Tzung-Bi Shih
2026-08-31 7:03 ` [PATCH 1/2] printk: Introduce CON_BYPASS_LOGLEVEL flag Tzung-Bi Shih
2026-08-31 7:03 ` [PATCH 2/2] pstore: Bypass loglevel suppression for pstore console Tzung-Bi Shih
2026-09-09 7:44 ` [PATCH 0/2] printk: Introduce loglevel bypass " Tzung-Bi Shih
2026-09-09 9:28 ` Petr Mladek [this message]
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=aqEmwXTLaTyUhhYG@pathway.suse.cz \
--to=pmladek@suse.com \
--cc=gpiccoli@igalia.com \
--cc=gregkh@linuxfoundation.org \
--cc=john.ogness@linutronix.de \
--cc=kees@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=senozhatsky@chromium.org \
--cc=tfiga@chromium.org \
--cc=tony.luck@intel.com \
--cc=tzungbi@kernel.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®