Re: [PATCH v7 2/2] hung_task: Always print basic hung task info header

On Wed, Aug 05, 2026 at 12:42:51AM +0800, Lance Yang wrote:
> 
> On Tue, Aug 04, 2026 at 11:54:06AM -0400, Aaron Tomlin wrote:
> >From: Petr Mladek <[email protected]>
> >
> >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.
> 
> I'd keep it simple and go with:
> 
> "
> hung_task: always print the blocked-task line
> 
> Once the warning budget is exhausted, hung_task_info() stops printing any
> per-task message. Detection still increments hung_task_detect_count and
> emits trace_sched_process_hang(), but dmesg no longer shows which task is
> blocked.
> 
> Move the "INFO: task ... blocked" line outside the budget check. Keep the
> rest of the per-task report budgeted and update the exhaustion message
> accordingly.
> "
> 
> [...]
> 
> Cheers, Lance

Acknowledged.

-- 
Aaron Tomlin