From: Andrew Morton <akpm@linux-foundation.org>
To: Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>,
Balbir Singh <balbir@linux.vnet.ibm.com>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
stable@kernel.org
Subject: Re: [BUGFIX] memcg: avoid deadlock between move charge and try_charge()
Date: Tue, 16 Nov 2010 12:41:17 -0800 [thread overview]
Message-ID: <20101116124117.64608b66.akpm@linux-foundation.org> (raw)
In-Reply-To: <20101116191748.d6645376.nishimura@mxp.nes.nec.co.jp>
On Tue, 16 Nov 2010 19:17:48 +0900
Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp> wrote:
> From: Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp>
>
> __mem_cgroup_try_charge() can be called under down_write(&mmap_sem)(e.g.
> mlock does it). This means it can cause deadlock if it races with move charge:
>
> Ex.1)
> move charge | try charge
> --------------------------------------+------------------------------
> mem_cgroup_can_attach() | down_write(&mmap_sem)
> mc.moving_task = current | ..
> mem_cgroup_precharge_mc() | __mem_cgroup_try_charge()
> mem_cgroup_count_precharge() | prepare_to_wait()
> down_read(&mmap_sem) | if (mc.moving_task)
> -> cannot aquire the lock | -> true
> | schedule()
>
> Ex.2)
> move charge | try charge
> --------------------------------------+------------------------------
> mem_cgroup_can_attach() |
> mc.moving_task = current |
> mem_cgroup_precharge_mc() |
> mem_cgroup_count_precharge() |
> down_read(&mmap_sem) |
> .. |
> up_read(&mmap_sem) |
> | down_write(&mmap_sem)
> mem_cgroup_move_task() | ..
> mem_cgroup_move_charge() | __mem_cgroup_try_charge()
> down_read(&mmap_sem) | prepare_to_wait()
> -> cannot aquire the lock | if (mc.moving_task)
> | -> true
> | schedule()
>
> To avoid this deadlock, we do all the move charge works (both can_attach() and
> attach()) under one mmap_sem section.
> And after this patch, we set/clear mc.moving_task outside mc.lock, because we
> use the lock only to check mc.from/to.
>
> Signed-off-by: Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp>
I put this in the send-to-Linus-in-about-a-week queue.
> Cc: <stable@kernel.org>
The patch doesn't apply well to 2.6.36 so if we do want it backported
then please prepare a tested backport for the -stable guys?
Thanks.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom policy in Canada: sign http://dissolvethecrtc.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2010-11-16 20:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-16 10:17 Daisuke Nishimura
2010-11-16 20:41 ` Andrew Morton [this message]
2010-11-17 0:24 ` Daisuke Nishimura
2010-11-26 7:48 ` [stable][BUGFIX] " Daisuke Nishimura
2010-12-06 22:46 ` [stable] [BUGFIX] " Greg KH
2010-11-17 0:11 ` KAMEZAWA Hiroyuki
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=20101116124117.64608b66.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=balbir@linux.vnet.ibm.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nishimura@mxp.nes.nec.co.jp \
--cc=stable@kernel.org \
/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