From: Hui Su <sh_def@163.com>
To: sashiko-reviews@lists.linux.dev
Cc: sched-ext@lists.linux.dev
Subject: Re: [PATCH] sched_ext: Hold DSQ refs for deferred reenqueues
Date: Thu, 01 Oct 2026 00:04:27 +0900 [thread overview]
Message-ID: <cc4b38f88a9e64e7bae930f8aca026f4.sh_def@163.com> (raw)
In-Reply-To: <20260930103603.DF9461F000FF@smtp.kernel.org>
> Sashiko AI review found 2 potential issues to consider:
> - [High] sched_ext: invalid wait context calling kfree() under raw_spinlock_t
> - [High] sched_ext: UAF due to missing memory barrier in deferred reenqueue
Agreed.
Please disregard this version. It has been superseded by a later revision:
https://lore.kernel.org/lkml/20260930143443.2862150-1-sh_def@163.com/
The later posting should have been tagged v2; I accidentally omitted the
version tag. Sorry for the confusion.
next prev parent reply other threads:[~2026-09-30 15:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-30 10:17 [PATCH] sched_ext: Hold DSQ refs for deferred reenqueues Hui Su
2026-09-30 10:36 ` sashiko-bot
2026-09-30 15:04 ` Hui Su [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-09-30 14:34 Hui Su
2026-09-30 15:20 ` Hui Su
2026-09-30 17:15 ` Tejun Heo
2026-10-08 3:41 ` Hui Su
2026-09-30 15:26 ` Andrea Righi
2026-10-08 3:38 ` Hui Su
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=cc4b38f88a9e64e7bae930f8aca026f4.sh_def@163.com \
--to=sh_def@163.com \
--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