Applying with these fixes on my side:
- dropped the dump_cpu_task() bullet
- the paragraph after the list now also covers a report that
  interrupts the CPU holding task_lock

On Mon, 16 Nov 2026 14:44:45 +0100, Denis V. Lunev <[email protected]> wrote:
>   - dump_cpu_task() shows the current task of a stuck CPU from the
>     RCU stall and CSD lock reports; when that task is stuck holding
>     its own task_lock, the report spins forever instead of printing;

dump_cpu_task() calls sched_show_task() only when
trigger_single_cpu_backtrace() returns false, and on x86_64 and arm64
it always returns true. This report never gets there on our kernels.

> An interrupt or softirq on the CPU holding task_lock that needs
> rnp->lock or pool->lock closes a lock cycle, and the node locks up
> hard in the middle of reporting a stall.

sysrq-t takes neither lock: it locks up when it interrupts the CPU
that holds task_lock, and so does the RCU stall report from the tick.
The paragraph now reads:

  A report run from an interrupt on the CPU holding task_lock spins on
  it, and an interrupt or softirq there that needs rnp->lock or
  pool->lock closes a lock cycle. Either way the node locks up hard in
  the middle of reporting a stall.

-- 
Konstantin Khorenko,
Virtuozzo Linux Kernel Team

_______________________________________________
Devel mailing list
[email protected]
https://lists.openvz.org/mailman/listinfo/devel

Reply via email to