From: Petr Mladek <pmladek@suse.com>
To: Aaron Tomlin <atomlin@atomlin.com>
Cc: akpm@linux-foundation.org, lance.yang@linux.dev,
mhiramat@kernel.org, gregkh@linuxfoundation.org,
joel.granados@kernel.org, sean@ashe.io,
linux-kernel@vger.kernel.org
Subject: Re: [v5 PATCH 2/2] hung_task: Enable runtime reset of hung_task_detect_count
Date: Thu, 8 Jan 2026 15:41:28 +0100 [thread overview]
Message-ID: <aV_CGOl_rXziqdHZ@pathway.suse.cz> (raw)
In-Reply-To: <20251231004125.2380105-3-atomlin@atomlin.com>
On Tue 2025-12-30 19:41:25, Aaron Tomlin wrote:
> Introduce support for writing to /proc/sys/kernel/hung_task_detect_count.
>
> Writing a value of zero to this file atomically resets the counter of
> detected hung tasks. This grants system administrators the ability to
> clear the cumulative diagnostic history after resolving an incident,
> simplifying monitoring without requiring a system restart.
> --- a/kernel/hung_task.c
> +++ b/kernel/hung_task.c
> @@ -36,7 +37,7 @@ static int __read_mostly sysctl_hung_task_check_count = PID_MAX_LIMIT;
> /*
> * Total number of tasks detected as hung since boot:
> */
> -static unsigned long __read_mostly sysctl_hung_task_detect_count;
> +static atomic_long_t sysctl_hung_task_detect_count = ATOMIC_LONG_INIT(0);
>
> /*
> * Limit number of tasks checked in a batch.
> @@ -246,20 +247,26 @@ static inline void hung_task_diagnostics(struct task_struct *t)
> }
>
> static void check_hung_task(struct task_struct *t, unsigned long timeout,
> - unsigned long prev_detect_count)
> + unsigned long prev_detect_count)
> {
> - unsigned long total_hung_task;
> + unsigned long total_hung_task, cur_detect_count;
>
> if (!task_is_hung(t, timeout))
> return;
>
> /*
> * This counter tracks the total number of tasks detected as hung
> - * since boot.
> + * since boot. If a reset occurred during the scan, we treat the
> + * current count as the new delta to avoid an underflow error.
> + * Ensure hang details are globally visible before the counter
> + * update.
> */
> - sysctl_hung_task_detect_count++;
> + cur_detect_count = atomic_long_inc_return_release(&sysctl_hung_task_detect_count);
The _release() feels a bit weird here because the counter might
get incremented more times during one scan.
IMHO, it should be perfectly fine to use the _relaxed version here
because it is in the middle of the acquire/release, see below.
The important thing here is that the load/modify/store operation
is done atomically.
> + if (cur_detect_count >= prev_detect_count)
> + total_hung_task = cur_detect_count - prev_detect_count;
> + else
> + total_hung_task = cur_detect_count;
>
> - total_hung_task = sysctl_hung_task_detect_count - prev_detect_count;
> trace_sched_process_hang(t);
>
> if (sysctl_hung_task_panic && total_hung_task >= sysctl_hung_task_panic) {
> @@ -318,10 +325,12 @@ static void check_hung_uninterruptible_tasks(unsigned long timeout)
> int max_count = sysctl_hung_task_check_count;
> unsigned long last_break = jiffies;
> struct task_struct *g, *t;
> - unsigned long prev_detect_count = sysctl_hung_task_detect_count;
> + unsigned long cur_detect_count, prev_detect_count, delta;
> int need_warning = sysctl_hung_task_warnings;
> unsigned long si_mask = hung_task_si_mask;
>
> + /* Acquire prevents reordering task checks before this point. */
> + prev_detect_count = atomic_long_read_acquire(&sysctl_hung_task_detect_count);
This value is read before the scan started => _acquire
semantic/barrier fits here.
> /*
> * If the system crashed already then all bets are off,
> * do not report extra hung tasks:
> @@ -346,7 +355,14 @@ static void check_hung_uninterruptible_tasks(unsigned long timeout)
> unlock:
> rcu_read_unlock();
>
> - if (!(sysctl_hung_task_detect_count - prev_detect_count))
> + /* Ensures we see all hang details recorded during the scan. */
> + cur_detect_count = atomic_long_read_acquire(&sysctl_hung_task_detect_count);
This value is read at the end of the scan => _release
semantic/barrier should be here.
> + if (cur_detect_count < prev_detect_count)
> + delta = cur_detect_count;
> + else
> + delta = cur_detect_count - prev_detect_count;
> +
> + if (!delta)
> return;
>
> if (need_warning || hung_task_call_panic) {
Otherwise, I do not have anything more to add. I agree with the other
proposals, for example:
+ remove 1st patch
+ split 2nd patch into two
+ changes in the sysctl code proposed by Joel
Best Regards,
Petr
next prev parent reply other threads:[~2026-01-08 14:41 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-31 0:41 [v5 PATCH 0/2] hung_task: Provide runtime reset interface for hung task detector Aaron Tomlin
2025-12-31 0:41 ` [v5 PATCH 1/2] hung_task: Introduce helper for hung task warning Aaron Tomlin
2026-01-01 9:49 ` Lance Yang
2026-01-01 19:28 ` Aaron Tomlin
2026-01-02 3:40 ` Lance Yang
2026-01-02 19:02 ` Aaron Tomlin
2025-12-31 0:41 ` [v5 PATCH 2/2] hung_task: Enable runtime reset of hung_task_detect_count Aaron Tomlin
2026-01-01 9:46 ` Lance Yang
2026-01-01 23:14 ` Joel Granados
2026-01-02 1:24 ` Aaron Tomlin
2026-01-05 10:53 ` Joel Granados
2026-01-05 14:42 ` Aaron Tomlin
2026-01-06 11:36 ` Joel Granados
2026-01-07 1:49 ` Aaron Tomlin
2026-01-06 11:51 ` Joel Granados
2026-01-07 3:37 ` Aaron Tomlin
2026-01-08 14:41 ` Petr Mladek [this message]
2026-01-09 13:50 ` Lance Yang
2026-01-12 13:13 ` Petr Mladek
2026-01-12 14:43 ` Lance Yang
2026-01-15 2:20 ` Aaron Tomlin
2026-01-10 15:55 ` 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=aV_CGOl_rXziqdHZ@pathway.suse.cz \
--to=pmladek@suse.com \
--cc=akpm@linux-foundation.org \
--cc=atomlin@atomlin.com \
--cc=gregkh@linuxfoundation.org \
--cc=joel.granados@kernel.org \
--cc=lance.yang@linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--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
all inboxes | Powered by JetHome®