From: Lance Yang <lance.yang@linux.dev>
To: atomlin@atomlin.com
Cc: akpm@linux-foundation.org, mhiramat@kernel.org, pmladek@suse.com,
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,
Lance Yang <lance.yang@linux.dev>
Subject: Re: [PATCH 2/2] hung_task: Always print basic hung task info header
Date: Tue, 4 Aug 2026 11:19:59 +0800 [thread overview]
Message-ID: <20260804031959.83680-1-lance.yang@linux.dev> (raw)
In-Reply-To: <20260804001542.249639-3-atomlin@atomlin.com>
On Mon, Aug 03, 2026 at 08:15:42PM -0400, Aaron Tomlin wrote:
>From: Petr Mladek <pmladek@suse.com>
>
>Currently, hung_task_info() completely suppresses any warning messages
>once the warning budget is reached. This leaves the system completely
>blind to any future hung tasks, even though we only wanted to suppress
>heavy process stack dumps.
>
>Modify hung_task_info() to always print the basic single-line error message
>about a hung task, regardless of whether the warning budget has been
>exhausted. Restrict only the verbose details (such as stack dumps,
>taint/release status, and blockers) to when the warning budget is intact
>or panic is triggered.
>
>Additionally, update the notice printed upon warning exhaustion to clarify
>that future reports will only omit process details rather than being completely
>suppressed.
>
>Assisted-by: gemini-3.5-flash
>Signed-off-by: Petr Mladek <pmladek@suse.com>
>---
Reviewed-by: Lance Yang <lance.yang@linux.dev>
prev parent reply other threads:[~2026-08-04 4:13 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
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 [this message]
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=20260804031959.83680-1-lance.yang@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.