From: Tejun Heo <tj@kernel.org>
To: tip-bot for Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp>
Cc: linux-tip-commits@vger.kernel.org, linux-kernel@vger.kernel.org,
hpa@zytor.com, mingo@redhat.com, a.p.zijlstra@chello.nl,
pjt@google.com, tglx@linutronix.de, mingo@elte.hu
Subject: Re: [tip:sched/core] sched: Fix cgroup movement of forking process
Date: Wed, 21 Dec 2011 09:26:32 -0800 [thread overview]
Message-ID: <20111221172632.GD9213@google.com> (raw)
In-Reply-To: <tip-4fc420c91f53e0a9f95665c6b14a1983716081e7@git.kernel.org>
Hello, guys.
On Wed, Dec 21, 2011 at 03:44:14AM -0800, tip-bot for Daisuke Nishimura wrote:
> sched: Fix cgroup movement of forking process
>
> There is a small race between task_fork_fair() and sched_move_task(),
> which is trying to move the parent.
>
> task_fork_fair() sched_move_task()
> --------------------------------+---------------------------------
> cfs_rq = task_cfs_rq(current)
> -> cfs_rq is the "old" one.
> curr = cfs_rq->curr
> -> curr is set to the parent.
> task_rq_lock()
> dequeue_task()
> ->parent.se.vruntime -= (old)cfs_rq->min_vruntime
> enqueue_task()
> ->parent.se.vruntime += (new)cfs_rq->min_vruntime
> task_rq_unlock()
> raw_spin_lock_irqsave(rq->lock)
> se->vruntime = curr->vruntime
> -> vruntime of the child is set to that of the parent
> which has already been updated by sched_move_task().
> se->vruntime -= (old)cfs_rq->min_vruntime.
> raw_spin_unlock_irqrestore(rq->lock)
>
> As a result, vruntime of the child becomes far bigger than expected,
> if (new)cfs_rq->min_vruntime >> (old)cfs_rq->min_vruntime.
>
> This patch fixes this problem by setting "cfs_rq" and "curr" after
> holding the rq->lock.
The race shouldn't happen with threadgroup locking scheduled to be
merged for the coming merge window. sched_fork() and cgroup migration
become exclusive and won't happen concurrently. Would still make
sense for -stable tho.
Thanks.
--
tejun
next prev parent reply other threads:[~2011-12-21 17:26 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-13 6:57 [PATCH 0/3] sched: some fixes for vruntime calculation related to cgroup movement Daisuke Nishimura
2011-12-13 6:57 ` [PATCH 1/3] sched: fix cgroup movement of newly created process Daisuke Nishimura
2011-12-13 12:01 ` Paul Turner
2011-12-14 1:04 ` Daisuke Nishimura
2011-12-13 12:41 ` Peter Zijlstra
2011-12-14 1:05 ` Daisuke Nishimura
2011-12-13 6:58 ` [PATCH 2/3] sched: fix cgroup movement of forking process Daisuke Nishimura
2011-12-13 12:22 ` Paul Turner
2011-12-13 6:59 ` [PATCH 3/3] sched: fix cgroup movement of waking process Daisuke Nishimura
2011-12-13 12:24 ` Paul Turner
2011-12-15 5:35 ` [PATCH -tip 0/3] sched: some fixes for vruntime calculation related to cgroup movement(v2) Daisuke Nishimura
2011-12-15 5:36 ` [PATCH 1/3] sched: fix cgroup movement of newly created process Daisuke Nishimura
2011-12-21 11:45 ` [tip:sched/core] sched: Fix " tip-bot for Daisuke Nishimura
2011-12-15 5:36 ` [PATCH 2/3] sched: fix cgroup movement of forking process Daisuke Nishimura
2011-12-21 11:44 ` [tip:sched/core] sched: Fix " tip-bot for Daisuke Nishimura
2011-12-21 17:26 ` Tejun Heo [this message]
2011-12-21 17:37 ` Tejun Heo
2011-12-22 1:54 ` Frederic Weisbecker
2011-12-22 2:01 ` Tejun Heo
2011-12-15 5:37 ` [PATCH 3/3] sched: fix cgroup movement of waking process Daisuke Nishimura
2011-12-21 11:45 ` [tip:sched/core] sched: Fix " tip-bot for Daisuke Nishimura
2011-12-19 2:55 ` [PATCH -tip 0/3] sched: some fixes for vruntime calculation related to cgroup movement(v2) Daisuke Nishimura
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=20111221172632.GD9213@google.com \
--to=tj@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--cc=nishimura@mxp.nes.nec.co.jp \
--cc=pjt@google.com \
--cc=tglx@linutronix.de \
/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