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: <z4w5bgiith2bonfofdqr5w2xasqoy4ooq2sbmr2gbihrfsvxw6@tgjys5bwg6fd>
Date: Wed, 30 Apr 2025 10:57:41 +0900
From: Sergey Senozhatsky <senozhatsky@...omium.org>
To: Petr Mladek <pmladek@...e.com>
Cc: 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>, 
	Tomasz Figa <tfiga@...omium.org>, John Ogness <john.ogness@...utronix.de>, 
	Steven Rostedt <rostedt@...dmis.org>, Andrew Morton <akpm@...ux-foundation.org>, 
	linux-kernel@...r.kernel.org, Sergey Senozhatsky <senozhatsky@...omium.org>
Subject: Re: [PATCH] hung_task: configurable hung-task stacktrace loglevel

On (25/04/30 10:34), Sergey Senozhatsky wrote:
[..]
> > int printk_report_start(const char *lvl)
> > {
> > 	int report_id = atomic_inc_return(&printk_report_count);
> > 
> > 	if (printk_force_report_loglevel)
> > 		printk_force_loglevel_enter(lvl);
> > 
> > 	printk("%s---------- Report No. %d start --------\n", lvl, report_id);
> > 
> > 	return report_id;
> > }
> > 
> > void printk_report_end(const char *lvl, int report_id)
> > {
> > 	printk("%s---------- Report No. %d end --------\n", lvl, report_id);
> > 
> > 	if (printk_force_report_loglevel)
> > 		printk_force_loglevel_exit();
> > }
> 
> Looks good to me, however
> 
> > My problem with the log level manipulation is that I do not know what
> > loglevel right.

We still might want to introduce CONFIG_CONSISTENT_REPORT_LOGLEVEL.