From: Greg KH <gregkh@linuxfoundation.org>
To: Lance Yang <lance.yang@linux.dev>
Cc: Aaron Tomlin <atomlin@atomlin.com>,
sean@ashe.io, linux-kernel@vger.kernel.org, mhiramat@kernel.org,
akpm@linux-foundation.org, Petr Mladek <pmladek@suse.com>
Subject: Re: [PATCH 1/2] hung_task: Consolidate hung task warning into an atomic log block
Date: Tue, 9 Dec 2025 15:56:58 +0900 [thread overview]
Message-ID: <2025120902-residence-maggot-c5f4@gregkh> (raw)
In-Reply-To: <c1a1f7d0-316f-40f5-8483-5fef1e4cdd60@linux.dev>
On Tue, Dec 09, 2025 at 01:12:14PM +0800, Lance Yang wrote:
>
>
> On 2025/12/9 12:12, Aaron Tomlin wrote:
> > Consolidate the multi-line console output in check_hung_task() into a new
> > helper function, hung_task_diagnostics().
> >
> > This patch ensures the entire diagnostic block (task info, kernel
> > version, and sysctl advice) is logged to the ring buffer via a single
> > pr_err() call. This is critical in a concurrent environment to prevent
> > message lines from interleaving with other CPU activity, thus
> > maintaining contextual integrity of the warning message.
> >
> > Signed-off-by: Aaron Tomlin <atomlin@atomlin.com>
> > ---
> > kernel/hung_task.c | 37 +++++++++++++++++++++++++++----------
> > 1 file changed, 27 insertions(+), 10 deletions(-)
> >
> > diff --git a/kernel/hung_task.c b/kernel/hung_task.c
> > index d2254c91450b..d5109a0994c5 100644
> > --- a/kernel/hung_task.c
> > +++ b/kernel/hung_task.c
> > @@ -223,6 +223,32 @@ static inline void debug_show_blocker(struct task_struct *task, unsigned long ti
> > }
> > #endif
> > +/**
> > + * hung_task_diagnostics - Print structured diagnostic info for a hung task.
> > + * @t: The struct task_struct of the detected hung task.
> > + *
> > + * This function consolidates the printing of core diagnostic information
> > + * for a task found to be blocked. This approach ensures atomic logging
> > + * of the multi-line message block, preventing interleaving by other
> > + * console activity, thus maintaining contextual clarity.
> > + */
> > +static void hung_task_diagnostics(struct task_struct *t)
> > +{
> > + unsigned long blocked_secs = (jiffies - t->last_switch_time) / HZ;
> > +
> > + pr_err("INFO: task %s:%d blocked for more than %ld seconds.\n"
> > + " %s %s %.*s\n"
> > + "%s\n"
>
> "%s\n" forces an unconditional newline, causing a spurious blank line when
> the flag isn't set, right?
The first \n should not be there, this should be all one line.
If you have multiple lines wanting to be printed, use multiple pr_err()
calls.
thanks,
greg k-h
next prev parent reply other threads:[~2025-12-09 6:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-09 4:12 [PATCH 0/2] hung_task: Provide runtime reset interface for hung task detector Aaron Tomlin
2025-12-09 4:12 ` [PATCH 1/2] hung_task: Consolidate hung task warning into an atomic log block Aaron Tomlin
2025-12-09 5:12 ` Lance Yang
2025-12-09 6:56 ` Greg KH [this message]
2025-12-09 22:14 ` Aaron Tomlin
2025-12-10 7:37 ` Greg KH
2025-12-10 13:08 ` Petr Mladek
2025-12-09 22:11 ` Aaron Tomlin
2025-12-09 4:12 ` [PATCH 2/2] hung_task: Provide runtime reset interface for hung task detector Aaron Tomlin
2025-12-09 4:54 ` Lance Yang
2025-12-09 22:06 ` Aaron Tomlin
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=2025120902-residence-maggot-c5f4@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=atomlin@atomlin.com \
--cc=lance.yang@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=pmladek@suse.com \
--cc=sean@ashe.io \
/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