From: Tahera Fahimi <taherafahimi@linux.microsoft.com>
To: stable@vger.kernel.org
Subject: Backport rcu-tasks fix to stable kernel version 6.6.y
Date: Thu, 11 Sep 2025 13:35:33 -0700 [thread overview]
Message-ID: <38f790d0-aae5-467f-bb1e-c7bd33ddffe7@linux.microsoft.com> (raw)
Dear Stable Kernel Maintainers,
I am writing to request the backport of the following patches to stable kernel versions 6.6.y,
addressing a deadlock issue in RCU Tasks related to do_exit() on preemptible systems.
Issue Description:
The kernel may experience deadlocks due to shared locking between exit_tasks_rcu_start() and
rcu_tasks_postscan() via synchronize_srcu(), when multiple processes exit concurrently. The problem
manifests as stalls in the RCU tasks grace period. This issue manifest as a deadlock in WSL kernel
which uses the stable kernel 6.6.87 (Please see the issue on https://github.com/microsoft/WSL/issues/13480)
Patches to Apply:
Patch 1:
Subject: rcu-tasks: Maintain lists to eliminate RCU-tasks/do_exit() deadlocks
Commit ID: 6b70399f9ef3809f6e308fd99dd78b072c1bd05c
Justification: Introduces per-CPU lists for exiting tasks, replacing SRCU-based waits and
eliminating deadlocks during concurrent exits.
Patch 2:
Subject: rcu-tasks: Eliminate deadlocks involving do_exit() and RCU tasks
Commit ID: 1612160b91272f5b1596f499584d6064bf5be794
Justification: Ensures all exiting tasks are properly gathered and synchronized, preventing
missed synchronizations and further deadlocks.
Patch 3:
Subject: rcu-tasks: Maintain real-time response in rcu_tasks_postscan()
Commit ID: 0bb11a372fc8d7006b4d0f42a2882939747bdbff
Justification: Periodically enables interrupts during per-CPU list traversal to maintain
system responsiveness, especially when many tasks are present.
Kernel version: latest kernel version in 6.6.y branch
Thank you for your consideration.
Best regards,
Tahera Fahimi
next reply other threads:[~2025-09-11 20:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-11 20:35 Tahera Fahimi [this message]
2025-09-13 11:48 ` Backport rcu-tasks fix to stable kernel version 6.6.y Greg KH
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=38f790d0-aae5-467f-bb1e-c7bd33ddffe7@linux.microsoft.com \
--to=taherafahimi@linux.microsoft.com \
--cc=stable@vger.kernel.org \
/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