From: Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: nishimura@mxp.nes.nec.co.jp, LKML <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.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: [RFC][PATCH 5/4] memcg: don't call res_counter_uncharge when obsolete
Date: Thu, 15 Jan 2009 11:14:20 +0900 [thread overview]
Message-ID: <20090115111420.8559bdb3.nishimura@mxp.nes.nec.co.jp> (raw)
In-Reply-To: <20090115110044.3a863af8.kamezawa.hiroyu@jp.fujitsu.com>
> > > To handle the problem "parent may be obsolete",
> > >
> > > call mem_cgroup_get(parent) at create()
> > > call mem_cgroup_put(parent) at freeing memcg.
> > > (regardless of use_hierarchy.)
> > >
> > > is clearer way to go, I think.
> > >
> > > I wonder whether there is mis-accounting problem or not..
> > >
> > > So, adding css_tryget() around problematic code can be a fix.
> > > --
> > > mem = swap_cgroup_record();
> > > if (css_tryget(&mem->css)) {
> > > res_counter_uncharge(&mem->memsw, PAZE_SIZE);
> > > css_put(&mem->css)
> > > }
> > > --
> > > I like css_tryget() rather than mem_cgroup_obsolete().
> > I agree.
> > The updated version is attached.
> >
> >
> > Thanks,
> > Daisuke nishimura.
> >
> > > To be honest, I'd like to remove memcg special stuff when I can.
> > >
> > > Thanks,
> > > -Kame
> > >
> > ===
> > From: Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp>
> >
> > mem_cgroup_get ensures that the memcg that has been got can be accessed
> > even after the directory has been removed, but it doesn't ensure that parents
> > of it can be accessed: parents might have been freed already by rmdir.
> >
> > This causes a bug in case of use_hierarchy==1, because res_counter_uncharge
> > climb up the tree.
> >
> > Check if the memcg is obsolete by css_tryget, and don't call
> > res_counter_uncharge when obsole.
> >
> > Signed-off-by: Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp>
> seems nice loock.
>
>
> > ---
> > mm/memcontrol.c | 15 ++++++++++++---
> > 1 files changed, 12 insertions(+), 3 deletions(-)
> >
> > diff --git a/mm/memcontrol.c b/mm/memcontrol.c
> > index fb62b43..4e3b100 100644
> > --- a/mm/memcontrol.c
> > +++ b/mm/memcontrol.c
> > @@ -1182,7 +1182,10 @@ int mem_cgroup_cache_charge(struct page *page, struct mm_struct *mm,
> > /* avoid double counting */
> > mem = swap_cgroup_record(ent, NULL);
> > if (mem) {
> > - res_counter_uncharge(&mem->memsw, PAGE_SIZE);
> > + if (!css_tryget(&mem->css)) {
> > + res_counter_uncharge(&mem->memsw, PAGE_SIZE);
> > + css_put(&mem->css);
> > + }
> > mem_cgroup_put(mem);
> > }
> > }
>
> I think css_tryget() returns "ture" at success....
>
> So,
> ==
> if (mem && css_tryget(&mem->css))
> res_counter....
>
> is correct.
>
> -Kame
>
Ooops! you are right.
Sorry for my silly mistake..
"mem" is checked beforehand, so I think css_tryget would be enough.
I'm now testing the attached one.
Thanks,
Daisuke Nishimura.
===
From: Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp>
mem_cgroup_get ensures that the memcg that has been got can be accessed
even after the directory has been removed, but it doesn't ensure that parents
of it can be accessed: parents might have been freed already by rmdir.
This causes a bug in case of use_hierarchy==1, because res_counter_uncharge
climb up the tree.
Check if the memcg is obsolete by css_tryget, and don't call
res_counter_uncharge when obsole.
Signed-off-by: Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp>
---
mm/memcontrol.c | 15 ++++++++++++---
1 files changed, 12 insertions(+), 3 deletions(-)
diff --git a/mm/memcontrol.c b/mm/memcontrol.c
index fb62b43..b9d5271 100644
--- a/mm/memcontrol.c
+++ b/mm/memcontrol.c
@@ -1182,7 +1182,10 @@ int mem_cgroup_cache_charge(struct page *page, struct mm_struct *mm,
/* avoid double counting */
mem = swap_cgroup_record(ent, NULL);
if (mem) {
- res_counter_uncharge(&mem->memsw, PAGE_SIZE);
+ if (css_tryget(&mem->css)) {
+ res_counter_uncharge(&mem->memsw, PAGE_SIZE);
+ css_put(&mem->css);
+ }
mem_cgroup_put(mem);
}
}
@@ -1252,7 +1255,10 @@ void mem_cgroup_commit_charge_swapin(struct page *page, struct mem_cgroup *ptr)
struct mem_cgroup *memcg;
memcg = swap_cgroup_record(ent, NULL);
if (memcg) {
- res_counter_uncharge(&memcg->memsw, PAGE_SIZE);
+ if (css_tryget(&memcg->css)) {
+ res_counter_uncharge(&memcg->memsw, PAGE_SIZE);
+ css_put(&memcg->css);
+ }
mem_cgroup_put(memcg);
}
@@ -1397,7 +1403,10 @@ void mem_cgroup_uncharge_swap(swp_entry_t ent)
memcg = swap_cgroup_record(ent, NULL);
if (memcg) {
- res_counter_uncharge(&memcg->memsw, PAGE_SIZE);
+ if (css_tryget(&memcg->css)) {
+ res_counter_uncharge(&memcg->memsw, PAGE_SIZE);
+ css_put(&memcg->css);
+ }
mem_cgroup_put(memcg);
}
}
--
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-15 2:30 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 [this message]
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
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=20090115111420.8559bdb3.nishimura@mxp.nes.nec.co.jp \
--to=nishimura@mxp.nes.nec.co.jp \
--cc=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=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