From: Andrew Morton <akpm@linux-foundation.org>
To: Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp>
Cc: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
LKML <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>,
Balbir Singh <balbir@linux.vnet.ibm.com>,
Pavel Emelyanov <xemul@openvz.org>,
Li Zefan <lizf@cn.fujitsu.com>, Paul Menage <menage@google.com>
Subject: Re: [BUGFIX][PATCH] memcg: get/put parents at create/free
Date: Thu, 15 Jan 2009 18:12:43 -0800 [thread overview]
Message-ID: <20090115181243.8dad9052.akpm@linux-foundation.org> (raw)
In-Reply-To: <20090116105009.7cabac46.nishimura@mxp.nes.nec.co.jp>
On Fri, 16 Jan 2009 10:50:09 +0900 Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp> wrote:
> This version works well in my test.
>
> Andrew, please pick up this one.
>
> ===
> From: Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp>
>
> The lifetime of struct cgroup and struct mem_cgroup is different and
> mem_cgroup has its own reference count for handling references from swap_cgroup.
>
> This causes strange problem that the parent mem_cgroup dies while
> child mem_cgroup alive, and this problem causes a bug in case of use_hierarchy==1
> because res_counter_uncharge climbs up the tree.
>
> This patch is for avoiding it by getting the parent at create, and
> putting it at freeing.
>
> Signed-off-by: Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp>
> Reviewed-by; KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
> ---
> mm/memcontrol.c | 23 ++++++++++++++++++++++-
> 1 files changed, 22 insertions(+), 1 deletions(-)
>
> diff --git a/mm/memcontrol.c b/mm/memcontrol.c
> index fb62b43..45e1b51 100644
> --- a/mm/memcontrol.c
> +++ b/mm/memcontrol.c
> @@ -202,6 +202,8 @@ pcg_default_flags[NR_CHARGE_TYPE] = {
>
> static void mem_cgroup_get(struct mem_cgroup *mem);
> static void mem_cgroup_put(struct mem_cgroup *mem);
> +static struct mem_cgroup *parent_mem_cgroup(struct mem_cgroup *mem);
> +static void mem_cgroup_get_parent(struct mem_cgroup *mem);
>
> static void mem_cgroup_charge_statistics(struct mem_cgroup *mem,
> struct page_cgroup *pc,
> @@ -2185,10 +2187,28 @@ static void mem_cgroup_get(struct mem_cgroup *mem)
>
> static void mem_cgroup_put(struct mem_cgroup *mem)
> {
> - if (atomic_dec_and_test(&mem->refcnt))
> + if (atomic_dec_and_test(&mem->refcnt)) {
> + struct mem_cgroup *parent = parent_mem_cgroup(mem);
> __mem_cgroup_free(mem);
> + if (parent)
> + mem_cgroup_put(parent);
> + }
> +}
> +
> +static struct mem_cgroup *parent_mem_cgroup(struct mem_cgroup *mem)
> +{
> + if (!mem->res.parent)
> + return NULL;
> + return mem_cgroup_from_res_counter(mem->res.parent, res);
> }
>
> +static void mem_cgroup_get_parent(struct mem_cgroup *mem)
> +{
> + struct mem_cgroup *parent = parent_mem_cgroup(mem);
> +
> + if (parent)
> + mem_cgroup_get(parent);
> +}
>
> #ifdef CONFIG_CGROUP_MEM_RES_CTLR_SWAP
> static void __init enable_swap_cgroup(void)
> @@ -2237,6 +2257,7 @@ mem_cgroup_create(struct cgroup_subsys *ss, struct cgroup *cont)
> if (parent)
> mem->swappiness = get_swappiness(parent);
> atomic_set(&mem->refcnt, 1);
> + mem_cgroup_get_parent(mem);
> return &mem->css;
> free_out:
> __mem_cgroup_free(mem);
It seems strange that we add a little helper function for the get(),
but open-code the put()?
--
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/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2009-01-16 2:12 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-13 9:45 [PATCH -rc] some fixes for memcg Daisuke Nishimura
2009-01-13 9:47 ` [PATCH 1/4] memcg: fix mem_cgroup_get_reclaim_stat_from_page Daisuke Nishimura
2009-01-13 9:48 ` [PATCH 2/4] memcg: fix error path of mem_cgroup_move_parent Daisuke Nishimura
2009-01-13 9:49 ` [PATCH 3/4] memcg: fix hierarchical reclaim Daisuke Nishimura
2009-01-13 9:50 ` [PATCH 4/4] memcg: make oom less frequently Daisuke Nishimura
2009-01-14 8:51 ` [RFC][PATCH 5/4] memcg: don't call res_counter_uncharge when obsolete Daisuke Nishimura
2009-01-14 13:43 ` KAMEZAWA Hiroyuki
2009-01-15 1:03 ` Daisuke Nishimura
2009-01-15 2:00 ` KAMEZAWA Hiroyuki
2009-01-15 2:14 ` Daisuke Nishimura
2009-01-15 4:38 ` Daisuke Nishimura
2009-01-15 5:14 ` KAMEZAWA Hiroyuki
2009-01-15 5:49 ` Balbir Singh
2009-01-15 6:39 ` KAMEZAWA Hiroyuki
2009-01-15 7:45 ` [RFC][PATCH] memcg: get/put parents at create/free Daisuke Nishimura
2009-01-15 7:54 ` KAMEZAWA Hiroyuki
2009-01-15 8:13 ` Daisuke Nishimura
2009-01-15 8:23 ` KAMEZAWA Hiroyuki
2009-01-15 8:51 ` Daisuke Nishimura
2009-01-15 9:10 ` KAMEZAWA Hiroyuki
2009-01-16 1:50 ` [BUGFIX][PATCH] " Daisuke Nishimura
2009-01-16 2:12 ` Andrew Morton [this message]
2009-01-16 2:17 ` KAMEZAWA Hiroyuki
2009-01-16 2:25 ` Daisuke Nishimura
2009-01-16 4:22 ` Daisuke Nishimura
2009-01-16 4:31 ` KAMEZAWA Hiroyuki
2009-01-14 13:55 ` [RFC][PATCH 5/4] memcg: don't call res_counter_uncharge when obsolete Balbir Singh
2009-01-15 2:48 ` KAMEZAWA Hiroyuki
2009-01-15 3:08 ` KAMEZAWA Hiroyuki
2009-01-15 3:24 ` KAMEZAWA Hiroyuki
2009-01-15 4:17 ` Balbir Singh
2009-01-15 4:41 ` KAMEZAWA Hiroyuki
2009-01-15 4:45 ` Balbir Singh
2009-01-15 4:54 ` KAMEZAWA Hiroyuki
2009-01-15 4:52 ` KAMEZAWA Hiroyuki
2009-01-15 5:17 ` Balbir Singh
2009-01-15 5:27 ` 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=20090115181243.8dad9052.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=lizf@cn.fujitsu.com \
--cc=menage@google.com \
--cc=nishimura@mxp.nes.nec.co.jp \
--cc=xemul@openvz.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;
as well as URLs for NNTP newsgroup(s).