From: "Kunwu Chan" <kunwu.chan@linux.dev>
To: "John Stultz" <jstultz@google.com>,
"LKML" <linux-kernel@vger.kernel.org>
Cc: "John Stultz" <jstultz@google.com>,
"Vineeth Pillai" <vineethrp@google.com>,
"Sonam Sanju" <sonam.sanju@intel.com>,
"Sean Christopherson" <seanjc@google.com>,
"Tejun Heo" <tj@kernel.org>,
"Joel Fernandes" <joelagnelf@nvidia.com>,
"Qais Yousef" <qyousef@layalina.io>,
"Ingo Molnar" <mingo@redhat.com>,
"Peter Zijlstra" <peterz@infradead.org>,
"Juri Lelli" <juri.lelli@redhat.com>,
"Vincent Guittot" <vincent.guittot@linaro.org>,
"Dietmar Eggemann" <dietmar.eggemann@arm.com>,
"Valentin Schneider" <vschneid@redhat.com>,
"Steven Rostedt" <rostedt@goodmis.org>,
"Will Deacon" <will@kernel.org>,
"Waiman Long" <longman@redhat.com>,
"Boqun Feng" <boqun.feng@gmail.com>,
"Paul E. McKenney" <paulmck@kernel.org>,
"Metin Kaya" <Metin.Kaya@arm.com>,
"Xuewen Yan" <xuewen.yan94@gmail.com>,
"K Prateek Nayak" <kprateek.nayak@amd.com>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Daniel Lezcano" <daniel.lezcano@linaro.org>,
"Suleiman Souhlal" <suleiman@google.com>,
"kuyo chang" <kuyo.chang@mediatek.com>,
"hupu" <hupu.gm@gmail.com>,
kernel-team@android.com
Subject: Re: [PATCH 0/2] Proxy Execution fixes for v7.1-rc
Date: Thu, 30 Apr 2026 09:56:27 +0000 [thread overview]
Message-ID: <919735cd6015f1057e076af00c615b6cdce0635d@linux.dev> (raw)
In-Reply-To: <20260427183848.698551-1-jstultz@google.com>
April 28, 2026 at 2:38 AM, "John Stultz" <jstultz@google.com mailto:jstultz@google.com?to=%22John%20Stultz%22%20%3Cjstultz%40google.com%3E > wrote:
>
> Hey All,
> So in testing with the full Proxy Execution series,
> Vineeth Pillai managed to trip some interesting bugs which
> initially looked to be KVM or RCU related[1], which he later
> diagnosed as Proxy Execution related and created a useful test
> driver to reproduce.
>
> I found these same issues could be triggered with the upstream
> portions of Proxy Execution, so I wanted to send along these
> fixes for 7.1-rc
>
> Again, a huge thanks to Vineeth for uncovering these issues
> that have evaded all my stress testing so far!
>
> Thanks
> -john
>
> [1]: https://lore.kernel.org/lkml/20260320125633.2290675-1-vineeth@bitbyteword.org/
>
Thanks John, Vineeth.
From the SRCU side, this helps explain the earlier KVM/RCU-looking
stall pattern as a downstream symptom, with trigger likely in
proxy-exec scheduler/mutex interaction.
It would be good to confirm whether the original workload still
reproduces (process_srcu pending + irqfd-side stalls) after applying
this series, and whether there is a proxy-exec on/off comparison
under the same setup.
Thanks for driving this down.
> Cc: Vineeth Pillai <vineethrp@google.com>
> Cc: Sonam Sanju <sonam.sanju@intel.com>
> Cc: Sean Christopherson <seanjc@google.com>
> Cc: Kunwu Chan <kunwu.chan@linux.dev>
> Cc: Tejun Heo <tj@kernel.org>
> Cc: Joel Fernandes <joelagnelf@nvidia.com>
> Cc: Qais Yousef <qyousef@layalina.io>
> Cc: Ingo Molnar <mingo@redhat.com>
> Cc: Peter Zijlstra <peterz@infradead.org>
> Cc: Juri Lelli <juri.lelli@redhat.com>
> Cc: Vincent Guittot <vincent.guittot@linaro.org>
> Cc: Dietmar Eggemann <dietmar.eggemann@arm.com>
> Cc: Valentin Schneider <vschneid@redhat.com>
> Cc: Steven Rostedt <rostedt@goodmis.org>
> Cc: Will Deacon <will@kernel.org>
> Cc: Waiman Long <longman@redhat.com>
> Cc: Boqun Feng <boqun.feng@gmail.com>
> Cc: "Paul E. McKenney" <paulmck@kernel.org>
> Cc: Metin Kaya <Metin.Kaya@arm.com>
> Cc: Xuewen Yan <xuewen.yan94@gmail.com>
> Cc: K Prateek Nayak <kprateek.nayak@amd.com>
> Cc: Thomas Gleixner <tglx@linutronix.de>
> Cc: Daniel Lezcano <daniel.lezcano@linaro.org>
> Cc: Suleiman Souhlal <suleiman@google.com>
> Cc: kuyo chang <kuyo.chang@mediatek.com>
> Cc: hupu <hupu.gm@gmail.com>
> Cc: kernel-team@android.com
>
> John Stultz (2):
> sched: proxy-exec: Close race causing workqueue work being delayed
> locking: mutex: Fix proxy-exec potentially deactivating tasks marked
> TASK_RUNNING
>
> kernel/locking/mutex.c | 1 +
> kernel/sched/core.c | 11 +++++++++++
> 2 files changed, 12 insertions(+)
>
> --
> 2.54.0.545.g6539524ca2-goog
>
prev parent reply other threads:[~2026-04-30 9:56 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-27 18:38 [PATCH 0/2] Proxy Execution fixes for v7.1-rc John Stultz
2026-04-27 18:38 ` [PATCH 1/2] sched: proxy-exec: Close race causing workqueue work being delayed John Stultz
2026-04-28 8:06 ` K Prateek Nayak
2026-04-28 9:43 ` Peter Zijlstra
2026-04-28 11:18 ` Peter Zijlstra
2026-04-28 13:15 ` K Prateek Nayak
2026-04-28 14:12 ` K Prateek Nayak
2026-04-28 16:50 ` Peter Zijlstra
2026-04-29 2:27 ` John Stultz
2026-04-29 8:59 ` K Prateek Nayak
2026-04-30 5:44 ` John Stultz
2026-04-30 5:47 ` John Stultz
2026-04-30 7:25 ` K Prateek Nayak
2026-04-30 21:05 ` John Stultz
2026-04-30 20:40 ` John Stultz
2026-05-01 5:57 ` K Prateek Nayak
2026-04-27 18:38 ` [PATCH 2/2] locking: mutex: Fix proxy-exec potentially deactivating tasks marked TASK_RUNNING John Stultz
2026-04-28 8:16 ` K Prateek Nayak
2026-04-28 19:50 ` John Stultz
2026-04-30 9:56 ` Kunwu Chan [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=919735cd6015f1057e076af00c615b6cdce0635d@linux.dev \
--to=kunwu.chan@linux.dev \
--cc=Metin.Kaya@arm.com \
--cc=boqun.feng@gmail.com \
--cc=daniel.lezcano@linaro.org \
--cc=dietmar.eggemann@arm.com \
--cc=hupu.gm@gmail.com \
--cc=joelagnelf@nvidia.com \
--cc=jstultz@google.com \
--cc=juri.lelli@redhat.com \
--cc=kernel-team@android.com \
--cc=kprateek.nayak@amd.com \
--cc=kuyo.chang@mediatek.com \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=mingo@redhat.com \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=qyousef@layalina.io \
--cc=rostedt@goodmis.org \
--cc=seanjc@google.com \
--cc=sonam.sanju@intel.com \
--cc=suleiman@google.com \
--cc=tglx@linutronix.de \
--cc=tj@kernel.org \
--cc=vincent.guittot@linaro.org \
--cc=vineethrp@google.com \
--cc=vschneid@redhat.com \
--cc=will@kernel.org \
--cc=xuewen.yan94@gmail.com \
/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