public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lance Yang <lance.yang@linux.dev>
To: Aaron Tomlin <atomlin@atomlin.com>
Cc: Petr Mladek <pmladek@suse.com>,
	neelx@suse.com, sean@ashe.io, mproche@gmail.com,
	chjohnst@gmail.com, nick.lange@gmail.com,
	linux-kernel@vger.kernel.org, mhiramat@kernel.org,
	joel.granados@kernel.org, gregkh@linuxfoundation.org,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] hung_task: Increment the global counter immediately
Date: Sat, 7 Feb 2026 14:10:35 +0800	[thread overview]
Message-ID: <74f33626-85c5-4bed-866d-1be20ecb09a5@linux.dev> (raw)
In-Reply-To: <6dgy332i25cmevxyq2rbhts4nygrr4w4ijbai7vppyrqwlhmag@rdleiex3o3ig>



On 2026/2/7 04:54, Aaron Tomlin wrote:
> On Wed, Feb 04, 2026 at 10:05:49AM -0800, Andrew Morton wrote:
>> On Wed, 4 Feb 2026 12:04:54 +0100 Petr Mladek <pmladek@suse.com> wrote:
>>
>>> A recent change allowed to reset the global counter of hung tasks using
>>> the sysctl interface. A potential race with the regular check has been
>>> solved by updating the global counter only once at the end of the check.
>>>
>>> However, the hung task check can take a significant amount of time,
>>> particularly when task information is being dumped to slow serial
>>> consoles. Some users monitor this global counter to trigger immediate
>>> migration of critical containers. Delaying the increment until the
>>> full check completes postpones these high-priority rescue operations.
>>>
>>> Update the global counter as soon as a hung task is detected. Since
>>> the value is read asynchronously, a relaxed atomic operation is
>>> sufficient.
>>>
>>> Reported-by: Lance Yang <lance.yang@linux.dev>
>>> Closes: https://lore.kernel.org/r/f239e00f-4282-408d-b172-0f9885f4b01b@linux.dev
>>> Signed-off-by: Petr Mladek <pmladek@suse.com>
>>> ---
>>> This is a followup patch for
>>> https://lore.kernel.org/r/20260125135848.3356585-1-atomlin@atomlin.com
>>>
>>> Note that I could not use commit IDs because the original
>>> patchset is not in a stable tree yet. In fact, it seems
>>> that it is not even in linux-next at the moment.
>>
>> Yes, I've gone into "fixes and trivial stuff only" mode, as we're at -rc8.
>>
>> Aaron, please incorporate Petr's fix into v8 and resend towards the end
>> of the merge window?
>>
>> Thanks.
> 
> Hi Andrew,
> 
> Absolutely.

Don't forget to credit Petr - just saying :)


  reply	other threads:[~2026-02-07  6:10 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-25 13:58 [v7 PATCH 0/2] hung_task: Provide runtime reset interface for hung task detector Aaron Tomlin
2026-01-25 13:58 ` [v7 PATCH 1/2] hung_task: Refactor detection logic and atomicise detection count Aaron Tomlin
2026-02-02  6:10   ` Masami Hiramatsu
2026-02-02 12:59   ` Petr Mladek
2026-02-03  3:05   ` Lance Yang
2026-02-03  3:08     ` Lance Yang
2026-02-03  9:03       ` Petr Mladek
2026-02-03 11:01         ` Lance Yang
2026-02-04 11:04           ` [PATCH] hung_task: Increment the global counter immediately Petr Mladek
2026-02-04 11:21             ` Lance Yang
2026-02-04 14:00             ` Aaron Tomlin
2026-02-04 18:05             ` Andrew Morton
2026-02-06 20:54               ` Aaron Tomlin
2026-02-07  6:10                 ` Lance Yang [this message]
2026-02-04 14:07         ` [v7 PATCH 1/2] hung_task: Refactor detection logic and atomicise detection count Aaron Tomlin
2026-01-25 13:58 ` [v7 PATCH 2/2] hung_task: Enable runtime reset of hung_task_detect_count Aaron Tomlin
2026-02-02  6:09   ` Masami Hiramatsu
2026-02-02 13:26   ` Petr Mladek
2026-02-01 19:48 ` [v7 PATCH 0/2] hung_task: Provide runtime reset interface for hung task detector 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=74f33626-85c5-4bed-866d-1be20ecb09a5@linux.dev \
    --to=lance.yang@linux.dev \
    --cc=akpm@linux-foundation.org \
    --cc=atomlin@atomlin.com \
    --cc=chjohnst@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=joel.granados@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhiramat@kernel.org \
    --cc=mproche@gmail.com \
    --cc=neelx@suse.com \
    --cc=nick.lange@gmail.com \
    --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