[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <xkd6ztswqkzbg5d2crhcg72gzmuuwiq36y2gyhxjnfmfkk6sli@awptl5aiukl6>
Date: Thu, 24 Apr 2025 16:11:44 +0900
From: Sergey Senozhatsky <senozhatsky@...omium.org>
To: Tomasz Figa <tfiga@...omium.org>
Cc: 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>, Steven Rostedt <rostedt@...dmis.org>,
Ben Segall <bsegall@...gle.com>, Mel Gorman <mgorman@...e.de>,
Valentin Schneider <vschneid@...hat.com>, linux-kernel@...r.kernel.org
Subject: Re: [RFC] sched: add sched_show_task() variant that accepts log level
On (25/04/24 13:34), Tomasz Figa wrote:
> > > Is there any reason why hung-task watchdog prints error header
> > > with KERN_ERR log level while task's backtrace is printed with
> > > KERN_INFO? Will it make sense to unify log levels and introduce
> > > sched_show_task() variant that accept log level param so that
> > > everything that hung-task watchdog prints becomes KERN_ERR?
> >
> > Thanks a lot for looking into this.
> >
> > Let me just add that I've been looking into ways to automatically
> > analyze kernel crash reports and I noticed that when I filter out
> > KERN_INFO and higher log levels, I end up losing useful information
> > for hung-task watchdog-kind of problems. This change would greatly
> > help in filtering out unnecessary noise from the logs.
> >
> > By the way, if having it as KERN_INFO by default would still be
> > desirable, I suppose we could add a KConfig option to set the desired
> > log level?
>
> Gentle ping on this patch.
Yeah, sorry.
Gentle `git send-email $1` on this.
$1 https://lore.kernel.org/linux-kernel/20250424070436.2380215-1-senozhatsky@chromium.org
Powered by blists - more mailing lists