From: Feng Tang <feng.tang@linux.alibaba.com>
To: Askar Safin <safinaskar@zohomail.com>
Cc: akpm <akpm@linux-foundation.org>, corbet <corbet@lwn.net>,
"john.ogness" <john.ogness@linutronix.de>,
"lance.yang" <lance.yang@linux.dev>,
linux-kernel <linux-kernel@vger.kernel.org>,
paulmck <paulmck@kernel.org>, pmladek <pmladek@suse.com>,
rostedt <rostedt@goodmis.org>
Subject: Re: [PATCH v3 1/5] panic: clean up code for console replay
Date: Tue, 15 Jul 2025 09:34:39 +0800 [thread overview]
Message-ID: <aHWwL7TdabnGna3D@U-2FWC9VHC-2323.local> (raw)
In-Reply-To: <1980ba9224c.11f5e5a9635585.8635674808464045994@zohomail.com>
On Tue, Jul 15, 2025 at 05:18:10AM +0400, Askar Safin wrote:
> ---- On Tue, 15 Jul 2025 04:49:12 +0400 Feng Tang <feng.tang@linux.alibaba.com> wrote ---
> > Thanks for trying the patch!
> I didn't try it. :) I merely run normal mainline or distro kernel in qemu.
>
> > My understanding is, 'console' have kind of different meaning in kernel
> > space than just /dev/console. In printk.c, you can see 'console' is
> > used everywhere, which are mostly bound to kernel message.like
> > console_try_replay_all(), console_flush_all(), console_flush_on_panic(),
> > which are consistent with the new name suggested by Petr.
> Okay, I agree.
>
> But I still kindly ask you to revert changes to Documentation/admin-guide/kernel-parameters.txt .
> Previous documentation is better.
> admin-guide is written for admins, not for kernel developers. And they understand "console" as /dev/console .
>
> I run kernel with panic_print=32 in hope that this will flush console (i. e. /dev/console), because this is how I interpreted
> your patched documentation. And I got different effect.
I see. How about changing the patch to:
- bit 5: print all printk messages in buffer
+ bit 5: replay all kernel messages on consoles at the end of panic
Thanks,
Feng
>
> --
> Askar Safin
> https://types.pl/@safinaskar
next prev parent reply other threads:[~2025-07-15 1:34 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-03 2:09 [PATCH v3 0/5] generalize panic_print's dump function to be used by other kernel parts Feng Tang
2025-07-03 2:10 ` [PATCH v3 1/5] panic: clean up code for console replay Feng Tang
2025-07-14 21:09 ` Askar Safin
2025-07-15 0:49 ` Feng Tang
2025-07-15 1:18 ` Askar Safin
2025-07-15 1:34 ` Feng Tang [this message]
2025-07-15 2:48 ` Askar Safin
2025-07-15 3:27 ` Feng Tang
2025-08-12 11:59 ` Petr Mladek
2025-08-13 0:43 ` Feng Tang
2025-07-03 2:10 ` [PATCH v3 2/5] panic: generalize panic_print's function to show sys info Feng Tang
2025-08-12 10:12 ` Petr Mladek
2025-07-03 2:10 ` [PATCH 3/5] panic: add 'panic_sys_info' sysctl to take human readable string parameter Feng Tang
2025-07-03 2:56 ` Lance Yang
2025-07-03 3:18 ` Feng Tang
2025-08-12 10:23 ` Petr Mladek
2025-08-13 0:39 ` Feng Tang
2025-07-03 2:10 ` [PATCH v3 4/5] panic: add 'panic_sys_info=' setup option for kernel cmdline Feng Tang
2025-08-12 10:31 ` Petr Mladek
2025-07-03 2:10 ` [PATCH v3 5/5] panic: add note that panic_print sysctl interface is deprecated Feng Tang
2025-08-12 11:52 ` Petr Mladek
2025-08-13 1:05 ` Feng Tang
2025-08-14 15:21 ` Petr Mladek
2025-07-03 3:23 ` [PATCH v3 0/5] generalize panic_print's dump function to be used by other kernel parts Lance Yang
2025-07-03 4:56 ` Lance Yang
2025-07-03 5:54 ` Feng Tang
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=aHWwL7TdabnGna3D@U-2FWC9VHC-2323.local \
--to=feng.tang@linux.alibaba.com \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=john.ogness@linutronix.de \
--cc=lance.yang@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@kernel.org \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=safinaskar@zohomail.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®