From: Lance Yang <lance.yang@linux.dev>
To: Aaron Tomlin <atomlin@atomlin.com>
Cc: sean@ashe.io, linux-kernel@vger.kernel.org, mhiramat@kernel.org,
akpm@linux-foundation.org, Petr Mladek <pmladek@suse.com>,
gregkh@linuxfoundation.org
Subject: Re: [PATCH 1/2] hung_task: Consolidate hung task warning into an atomic log block
Date: Tue, 9 Dec 2025 13:12:14 +0800 [thread overview]
Message-ID: <c1a1f7d0-316f-40f5-8483-5fef1e4cdd60@linux.dev> (raw)
In-Reply-To: <20251209041218.1583600-2-atomlin@atomlin.com>
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?
> + "\"echo 0 > /proc/sys/kernel/hung_task_timeout_secs\""
> + " disables this message.\n",
> + t->comm, t->pid, blocked_secs,
> + print_tainted(), init_utsname()->release,
> + (int)strcspn(init_utsname()->version, " "),
> + init_utsname()->version,
> + (t->flags & PF_POSTCOREDUMP) ?
> + " Blocked by coredump." : "");
> +}
> +
> static void check_hung_task(struct task_struct *t, unsigned long timeout,
> unsigned long prev_detect_count)
> {
> @@ -252,16 +278,7 @@ static void check_hung_task(struct task_struct *t, unsigned long timeout,
> if (sysctl_hung_task_warnings || hung_task_call_panic) {
> if (sysctl_hung_task_warnings > 0)
> sysctl_hung_task_warnings--;
> - pr_err("INFO: task %s:%d blocked for more than %ld seconds.\n",
> - t->comm, t->pid, (jiffies - t->last_switch_time) / HZ);
> - pr_err(" %s %s %.*s\n",
> - print_tainted(), init_utsname()->release,
> - (int)strcspn(init_utsname()->version, " "),
> - init_utsname()->version);
> - if (t->flags & PF_POSTCOREDUMP)
> - pr_err(" Blocked by coredump.\n");
> - pr_err("\"echo 0 > /proc/sys/kernel/hung_task_timeout_secs\""
> - " disables this message.\n");
> + hung_task_diagnostics(t);
Since there's only one caller, why not just open-code it ...
TBH, jamming everything into a single pr_err() call doesn't look any
cleaner to me than the original code :(
> sched_show_task(t);
> debug_show_blocker(t, timeout);
>
Cheers,
Lance
next prev parent reply other threads:[~2025-12-09 5:12 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 [this message]
2025-12-09 6:56 ` Greg KH
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=c1a1f7d0-316f-40f5-8483-5fef1e4cdd60@linux.dev \
--to=lance.yang@linux.dev \
--cc=akpm@linux-foundation.org \
--cc=atomlin@atomlin.com \
--cc=gregkh@linuxfoundation.org \
--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