From: Tao Cui <cui.tao@linux.dev>
To: Tejun Heo <tj@kernel.org>
Cc: cui.tao@linux.dev, Tao Cui <cuitao@kylinos.cn>,
void@manifault.com, arighi@nvidia.com, changwoo@igalia.com,
sched-ext@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] sched_ext: don't rehome a dead task in scx_cgroup_task_migrated
Date: Sat, 15 Aug 2026 11:31:34 +0800 [thread overview]
Message-ID: <9b5da7b7-5cd9-4a01-9977-f40fb2e7e279@linux.dev> (raw)
In-Reply-To: <71d1c173b538ca29d783232d89464d7a@kernel.org>
Hi,
在 2026/8/15 03:04, Tejun Heo 写道:
> Hello,
>
> On Tue, Aug 11, 2026 at 06:31:22PM +0800, Tao Cui wrote:
>> A task can exit between cgroup migration commit and the MIGRATED callback:
>> sched_ext_dead() marks it SCX_TASK_DEAD before cgroup_task_dead() removes it
>> from the migration list, so scx_cgroup_task_migrated() can pick up a dead
>> task and call scx_rehome_task(), which re-enables it and leaks the BPF
>> scheduler's per-task resources. The other scx_rehome_task() callers already
>> check for this; do the same here.
>
> I don't think this window exists. SCX_TASK_DEAD is set only by
> sched_ext_dead() from finish_task_switch(), which a task reaches only
> after exit_signals(), and exit_signals() sets PF_EXITING inside
> cgroup_threadgroup_change_begin(). The MIGRATED notifiers run inside
> cgroup_migrate_execute() with the same rwsem write-held through
> cgroup_attach_lock(), so no task in the set can enter the exit path
> until the migration is done. Tasks which were already exiting are
> filtered out by the PF_EXITING test in cgroup_migrate_add_task().
>
> The DEAD tests you referenced are in scx_task_iter walks which run
> without the threadgroup rwsem, where dying tasks can actually show up.
>
> Did you try to reproduce the leak? When code review turns up a
> suspected bug, it's a good idea to reproduce it first to verify the
> assumptions before writing a fix.
>
You're right, I missed that.
I walked it again, a task past exit_signals() is filtered out by the PF_EXITING test in cgroup_migrate_add_task(), and a task mid-migration can't reach exit_signals() until the rwsem is dropped, so scx_cgroup_task_migrated() always sees a live task. The DEAD checks I pointed at are on task iteration paths without the rwsem, so they don't apply here.
I didn't try to reproduce the leak first. I will next time.
Please disregard this patch.Sorry for the noise.
Thanks,
Tao> Thanks.
>
> --
> tejun
prev parent reply other threads:[~2026-08-15 3:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-11 10:31 Tao Cui
2026-08-14 19:04 ` Tejun Heo
2026-08-15 3:31 ` Tao Cui [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=9b5da7b7-5cd9-4a01-9977-f40fb2e7e279@linux.dev \
--to=cui.tao@linux.dev \
--cc=arighi@nvidia.com \
--cc=changwoo@igalia.com \
--cc=cuitao@kylinos.cn \
--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®