LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Zhang Qiao <zhangqiao22@huawei.com>
Cc: mingo@redhat.com, juri.lelli@redhat.com,
vincent.guittot@linaro.org, linux-kernel@vger.kernel.org,
tj@kernel.org
Subject: Re: [PATCH] kernel/sched: Fix sched_fork() access an invalid sched_task_group
Date: Mon, 30 Aug 2021 16:39:54 +0200 [thread overview]
Message-ID: <YSztujInfNNXkG5/@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20210826112635.7404-1-zhangqiao22@huawei.com>
On Thu, Aug 26, 2021 at 07:26:35PM +0800, Zhang Qiao wrote:
> There is a small race between copy_process() and sched_fork()
> where child->sched_task_group point to an already freed pointer.
>
> parent doing fork() | someone moving the parent
> to another cgroup
> -------------------------------+-------------------------------
> copy_process()
> + dup_task_struct()<1>
> parent move to another cgroup,
> and free the old cgroup. <2>
> + sched_fork()
> + __set_task_cpu()<3>
> + task_fork_fair()
> + sched_slice()<4>
>
> In the worst case, this bug can lead to "use-after-free" and
> cause panic as shown above,
> (1)parent copy its sched_task_group to child at <1>;
> (2)someone move the parent to another cgroup and free the old
> cgroup at <2>;
> (3)the sched_task_group and cfs_rq that belong to the old cgroup
> will be accessed at <3> and <4>, which cause a panic:
>
> [89249.732198] BUG: unable to handle kernel NULL pointer
> dereference at 0000000000000000
> [89249.732701] PGD 8000001fa0a86067 P4D 8000001fa0a86067 PUD
> 2029955067 PMD 0
> [89249.733005] Oops: 0000 [#1] SMP PTI
> [89249.733288] CPU: 7 PID: 648398 Comm: ebizzy Kdump: loaded
> Tainted: G OE --------- - - 4.18.0.x86_64+ #1
> [89249.734318] RIP: 0010:sched_slice+0x84/0xc0
> ....
> [89249.737910] Call Trace:
> [89249.738181] task_fork_fair+0x81/0x120
> [89249.738457] sched_fork+0x132/0x240
> [89249.738732] copy_process.part.5+0x675/0x20e0
> [89249.739010] ? __handle_mm_fault+0x63f/0x690
> [89249.739286] _do_fork+0xcd/0x3b0
> [89249.739558] do_syscall_64+0x5d/0x1d0
> [89249.739830] entry_SYSCALL_64_after_hwframe+0x65/0xca
> [89249.740107] RIP: 0033:0x7f04418cd7e1
>
> When a new process is forked, cgroup_post_fork() associates it
> with the cgroup of its parent. Therefore this commit move the
> __set_task_cpu() and task_fork() that access some cgroup-related
> fields(sched_task_group and cfs_rq) to sched_post_fork() and
> call sched_post_fork() after cgroup_post_fork().
>
> Fixes: 8323f26ce342 ("sched: Fix race in task_group")
> Signed-off-by: Zhang Qiao <zhangqiao22@huawei.com>
Hmm, I think you're right. Did something recently chagne in cgroup land
to make this more visible? This code hasn't changed in like 9 years.
next prev parent reply other threads:[~2021-08-30 14:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-26 11:26 Zhang Qiao
2021-08-30 11:49 ` Zhang Qiao
2021-08-30 14:39 ` Peter Zijlstra [this message]
2021-08-30 17:32 ` Tejun Heo
2021-08-31 7:58 ` Zhang Qiao
2021-08-31 22:59 ` Tejun Heo
2021-09-01 7:43 ` Zhang Qiao
2021-09-01 16:45 ` Tejun Heo
2021-09-02 7:42 ` Zhang Qiao
2021-09-07 17:01 ` Tejun Heo
2021-09-08 11:32 ` Zhang Qiao
2021-09-08 16:29 ` Tejun Heo
2021-09-09 9:45 ` Zhang Qiao
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=YSztujInfNNXkG5/@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tj@kernel.org \
--cc=vincent.guittot@linaro.org \
--cc=zhangqiao22@huawei.com \
--subject='Re: [PATCH] kernel/sched: Fix sched_fork() access an invalid sched_task_group' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).