The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Lance Yang <lance.yang@linux.dev>
To: Aaron Tomlin <atomlin@atomlin.com>
Cc: linux-kernel@vger.kernel.org, david.laight.linux@gmail.com,
	neelx@suse.com, sean@ashe.io, chjohnst@gmail.com, steve@abita.co,
	mproche@gmail.com, nick.lange@gmail.com,
	akpm@linux-foundation.org, mhiramat@kernel.org, pmladek@suse.com
Subject: Re: [PATCH 1/2] hung_task: Reset warning budget when problem gets resolved
Date: Tue, 4 Aug 2026 10:24:01 +0800	[thread overview]
Message-ID: <6b7d5ce8-309c-46d7-ae7a-df38b733839c@linux.dev> (raw)
In-Reply-To: <20260804001542.249639-2-atomlin@atomlin.com>



On 2026/8/4 08:15, Aaron Tomlin wrote:
> From: Petr Mladek <pmladek@suse.com>
> 
> sysctl_hung_task_warnings counts how many hung tasks are reported.
> The watchdog does not report anything once the limit is reached.
> Currently, this budget is decremented permanently, meaning the kernel is
> left blind to subsequent hung tasks even after the original issue resolves.
> 
> Keep the global sysctl_hung_task_warnings intact, and instead decrement
> a copy (hung_task_warnings_printed) when warnings are printed. Reset
> the copy back to the configured sysctl_hung_task_warnings limit once the
> problem on the system gets resolved and check_hung_uninterruptible_tasks()
> detects no hung tasks in a check interval.
> 
> Also keep the copy updated when the global sysctl_hung_task_warnings
> value is updated via sysctl, and update documentation to reflect
> the new behavior.
> 
> Assisted-by: gemini-3.5-flash
> Signed-off-by: Petr Mladek <pmladek@suse.com>

Was a bit surprised not to see any tag from you here. I’d assumed you’d
be taking this through testing and spinning v7, so I expected your SoB +
Suggested-by Petr.

Keeping both SoBs works too; either way, you’ve definitely earned yours
here.

Assisted-by: gemini-3.5-flash
Suggested-by: Petr Mladek <pmladek@suse.com>
Signed-off-by: Aaron Tomlin <atomlin@atomlin.com>

Same goes for patch #02, btw :)

Thanks, Lance

  reply	other threads:[~2026-08-04  2:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-04  0:15 [PATCH 0/2] hung_task: Improve warning budget handling and task reporting Aaron Tomlin
2026-08-04  0:15 ` [PATCH 1/2] hung_task: Reset warning budget when problem gets resolved Aaron Tomlin
2026-08-04  2:24   ` Lance Yang [this message]
2026-08-04 14:19     ` Aaron Tomlin
2026-08-04  3:18   ` Lance Yang
2026-08-04 14:54     ` Aaron Tomlin
2026-08-04  0:15 ` [PATCH 2/2] hung_task: Always print basic hung task info header Aaron Tomlin
2026-08-04  3:19   ` Lance Yang

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=6b7d5ce8-309c-46d7-ae7a-df38b733839c@linux.dev \
    --to=lance.yang@linux.dev \
    --cc=akpm@linux-foundation.org \
    --cc=atomlin@atomlin.com \
    --cc=chjohnst@gmail.com \
    --cc=david.laight.linux@gmail.com \
    --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 \
    --cc=steve@abita.co \
    /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