public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: linux-kernel@vger.kernel.org, kernel-team@meta.com,
	sched-ext@meta.com, David Vernet <void@manifault.com>,
	Andrea Righi <arighi@nvidia.com>,
	Changwoo Min <changwoo@igalia.com>
Subject: Re: [PATCH sched_ext/for-6.14-fixes] sched_ext: Fix incorrect autogroup migration detection
Date: Mon, 27 Jan 2025 08:33:06 -1000	[thread overview]
Message-ID: <Z5fRYoOCySEbkUWR@slm.duckdns.org> (raw)
In-Reply-To: <Z5QSlNthLXQdhdew@slm.duckdns.org>

On Fri, Jan 24, 2025 at 12:22:12PM -1000, Tejun Heo wrote:
> scx_move_task() is called from sched_move_task() and tells the BPF scheduler
> that cgroup migration is being committed. sched_move_task() is used by both
> cgroup and autogroup migrations and scx_move_task() tried to filter out
> autogroup migrations by testing the destination cgroup and PF_EXITING but
> this is not enough. In fact, without explicitly tagging the thread which is
> doing the cgroup migration, there is no good way to tell apart
> scx_move_task() invocations for racing migration to the root cgroup and an
> autogroup migration.
> 
> This led to scx_move_task() incorrectly ignoring a migration from non-root
> cgroup to an autogroup of the root cgroup triggering the following warning:
> 
>   WARNING: CPU: 7 PID: 1 at kernel/sched/ext.c:3725 scx_cgroup_can_attach+0x196/0x340
>   ...
>   Call Trace:
>   <TASK>
>     cgroup_migrate_execute+0x5b1/0x700
>     cgroup_attach_task+0x296/0x400
>     __cgroup_procs_write+0x128/0x140
>     cgroup_procs_write+0x17/0x30
>     kernfs_fop_write_iter+0x141/0x1f0
>     vfs_write+0x31d/0x4a0
>     __x64_sys_write+0x72/0xf0
>     do_syscall_64+0x82/0x160
>     entry_SYSCALL_64_after_hwframe+0x76/0x7e
> 
> Fix it by adding an argument to sched_move_task() that indicates whether the
> moving is for a cgroup or autogroup migration. After the change,
> scx_move_task() is called only for cgroup migrations and renamed to
> scx_cgroup_move_task().
> 
> Link: https://github.com/sched-ext/scx/issues/370
> Fixes: 819513666966 ("sched_ext: Add cgroup support")
> Cc: stable@vger.kernel.org # v6.12+
> Signed-off-by: Tejun Heo <tj@kernel.org>

Applied to sched_ext/for-6.14-fixes.

Thanks.

-- 
tejun

      parent reply	other threads:[~2025-01-27 18:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-24 22:22 [PATCH sched_ext/for-6.14-fixes] sched_ext: Fix incorrect autogroup migration detection Tejun Heo
2025-01-27 11:24 ` Peter Zijlstra
2025-01-27 18:33 ` Tejun Heo [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=Z5fRYoOCySEbkUWR@slm.duckdns.org \
    --to=tj@kernel.org \
    --cc=arighi@nvidia.com \
    --cc=changwoo@igalia.com \
    --cc=kernel-team@meta.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=sched-ext@meta.com \
    --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