linux-kernel - Re: printk: selective deactivation of feature ignoring non panic cpu's messages

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20250304020112.GA4025668@tiffany>
Date: Tue, 4 Mar 2025 11:01:12 +0900
From: Donghyeok Choe <d7271.choe@...sung.com>
To: John Ogness <john.ogness@...utronix.de>, pmladek@...e.com
Cc: linux-kernel@...r.kernel.org, takakura@...inux.co.jp,
	youngmin.nam@...sung.com, hajun.sung@...sung.com, seungh.jung@...sung.com,
	jh1012.choi@...sung.com
Subject: Re: printk: selective deactivation of feature ignoring non panic
 cpu's messages

On Fri, Feb 28, 2025 at 03:26:34PM +0106, John Ogness wrote:
> Perhaps Donghyeok might be happy enough if the debug option simply
> allowed the non-panic CPUs to store records. There are plenty of tools
> available to get at the dmesg buffer.

That's right. Just the addition of debug options can make me very happy.
If I find any problems using debug option on, I'll share them with you
immediately.

First, Shall we reflect only the patch that adds our debug option?
I will also study the problems raised. I want to be able to
participate in your discussion someday.

Thank you.