linux-kernel - Re: [PATCH] hung_task: configurable hung-task stacktrace loglevel

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: <ex23fyhfgsdapar3vg2nohkkqgxzbvawh47mvzxkxlhgyaksjv@n2a5omy7wjn7>
Date: Wed, 30 Apr 2025 14:05:39 +0900
From: Sergey Senozhatsky <senozhatsky@...omium.org>
To: John Ogness <john.ogness@...utronix.de>
Cc: Petr Mladek <pmladek@...e.com>, Tomasz Figa <tfiga@...omium.org>, 
	Sergey Senozhatsky <senozhatsky@...omium.org>, Ingo Molnar <mingo@...hat.com>, 
	Peter Zijlstra <peterz@...radead.org>, Juri Lelli <juri.lelli@...hat.com>, 
	Vincent Guittot <vincent.guittot@...aro.org>, Dietmar Eggemann <dietmar.eggemann@....com>, 
	Ben Segall <bsegall@...gle.com>, Mel Gorman <mgorman@...e.de>, 
	Steven Rostedt <rostedt@...dmis.org>, Andrew Morton <akpm@...ux-foundation.org>, 
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] hung_task: configurable hung-task stacktrace loglevel

On (25/04/28 10:11), John Ogness wrote:
> On 2025-04-25, Petr Mladek <pmladek@...e.com> wrote:
> > I am afraid that manipulating log levels is a lost fight because
> > different people might have different opinion about how various
> > messages are important.
> 
> Wasn't that the whole point of Sergey's patch? To make it configurable?
> 
> I must admit that I am not happy with the patch.

Same here ;)

[..]
> In other words, I would prefer to recycle the emergenceny enter/exit
> markers rather than introduce new ones. (Unless we are also talking
> about reports that are totally normal and acceptable during runtime.)

Adding "--- report begin ---"/"--- report end ---" markers everywhere
probably will suffice.  Paired with printk-owner these should make
log parsing error level independent, I guess.