From: Tejun Heo <tj@kernel.org>
To: sashiko-reviews@lists.linux.dev
Cc: sashiko-bot@kernel.org, sched-ext@lists.linux.dev
Subject: Re: [PATCH sched_ext/for-7.3-fixes] sched_ext: Fix use-after-free of a destroyed user DSQ by a deferred reenqueue
Date: Fri, 09 Oct 2026 12:40:50 -1000 [thread overview]
Message-ID: <fce83a32347037f85ea4ba13e6e75765@kernel.org> (raw)
In-Reply-To: <sashiko-outbox-166126@kernel.org>
Hello,
On Fri, Oct 09, 2026 at 10:09:59PM +0000, sashiko-bot@kernel.org wrote:
> Does this code compile when CONFIG_SCHED_CLASS_EXT is enabled? Looking at struct
> scx_dispatch_q defined in include/linux/sched/ext.h, it appears the correct
> member name is pcpu_user, not pcpu. Using dsq->pcpu might result in an
> unconditional build failure.
The patch is against sched_ext/for-7.3-fixes, where the member is still
pcpu. 92344fad5b54 ("sched_ext: Skip per-CPU data allocation for built-in
DSQs") renamed it to pcpu_user in for-7.4. The merge into for-7.4 will
carry the rename.
Thanks.
--
tejun
next prev parent reply other threads:[~2026-10-09 22:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-09 22:01 [PATCH sched_ext/for-7.3-fixes] sched_ext: Fix use-after-free of a destroyed user DSQ by a deferred reenqueue Tejun Heo
2026-10-09 22:09 ` sashiko-bot
2026-10-09 22:40 ` Tejun Heo [this message]
2026-10-10 6:23 ` [PATCH] " Hui Su
2026-10-10 8:38 ` [PATCH sched_ext/for-7.3-fixes] " 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=fce83a32347037f85ea4ba13e6e75765@kernel.org \
--to=tj@kernel.org \
--cc=sashiko-bot@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=sched-ext@lists.linux.dev \
/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