From: Cheng-Yang Chou <yphbchou0911@gmail.com>
To: Andrea Righi <arighi@nvidia.com>
Cc: Tejun Heo <tj@kernel.org>, David Vernet <void@manifault.com>,
Changwoo Min <changwoo@igalia.com>,
sched-ext@lists.linux.dev, linux-kernel@vger.kernel.org,
Ching-Chun Huang <jserv@ccns.ncku.edu.tw>,
Chia-Ping Tsai <chia7712@gmail.com>,
chengyang.chou@mediatek.com
Subject: Re: [PATCH sched_ext/for-7.3-fixes] sched_ext: Unlink pending local reenqueues before freeing scheduler
Date: Thu, 17 Sep 2026 00:33:47 +0800 [thread overview]
Message-ID: <20260917002903.Gf17f@cchengyang.duckdns.org> (raw)
In-Reply-To: <20260916145807.3250167-1-arighi@nvidia.com>
Hi Andrea,
On Wed, Sep 16, 2026 at 04:58:07PM +0200, Andrea Righi wrote:
[...]
> @@ -5380,13 +5380,20 @@ static void scx_sched_free_rcu_work(struct work_struct *work)
>
> for_each_possible_cpu(cpu) {
> struct scx_sched_pcpu *pcpu = per_cpu_ptr(sch->pcpu, cpu);
> + struct rq *rq = cpu_rq(cpu);
>
> /*
> - * $sch would have entered bypass mode before the RCU grace
> - * period. As that blocks new deferrals, all
> - * deferred_reenq_local_node's must be off-list by now.
> + * Bypass blocks new deferrals, but a request queued before bypass
> + * may still be pending. As run_deferred() runs under the rq lock,
> + * take it to wait for any in-flight processing before unlinking the
> + * now-obsolete request.
> */
> - WARN_ON_ONCE(!list_empty(&pcpu->deferred_reenq_local.node));
> + scoped_guard (rq_lock_irqsave, rq) {
> + guard(raw_spinlock)(&rq->scx.deferred_reenq_lock);
> +
> + if (!list_empty(&pcpu->deferred_reenq_local.node))
> + list_del_init(&pcpu->deferred_reenq_local.node);
> + }
>
> /* remove the queued ecaps sync so the pcpu can be freed */
> scx_discard_ecaps_to_sync(cpu, pcpu);
> @@ -5395,7 +5402,7 @@ static void scx_sched_free_rcu_work(struct work_struct *work)
> * Bypass blocks new kicks. Flush the kick irq_work so this
> * pcpu's to_kick_node is off the list before it is freed.
> */
> - irq_work_sync(&cpu_rq(cpu)->scx.kick_cpus_irq_work);
> + irq_work_sync(&rq->scx.kick_cpus_irq_work);
> WARN_ON_ONCE(!list_empty(&pcpu->to_kick_node));
> free_cpumask_var(pcpu->cpus_to_kick);
> free_cpumask_var(pcpu->cpus_to_kick_if_idle);
> --
> 2.55.0
>
Though I couldn't reproduce the issue on my end, the fix lgtm. Thanks!
Acked-by: Cheng-Yang Chou <yphbchou0911@gmail.com>
--
Cheers,
Cheng-Yang
next prev parent reply other threads:[~2026-09-16 16:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-16 14:58 Andrea Righi
2026-09-16 16:33 ` Cheng-Yang Chou [this message]
2026-09-16 22:00 ` Tejun Heo
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=20260917002903.Gf17f@cchengyang.duckdns.org \
--to=yphbchou0911@gmail.com \
--cc=arighi@nvidia.com \
--cc=changwoo@igalia.com \
--cc=chengyang.chou@mediatek.com \
--cc=chia7712@gmail.com \
--cc=jserv@ccns.ncku.edu.tw \
--cc=linux-kernel@vger.kernel.org \
--cc=sched-ext@lists.linux.dev \
--cc=tj@kernel.org \
--cc=void@manifault.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
all inboxes | Powered by JetHome®