From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
To: Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp>
Cc: Hugh Dickins <hugh@veritas.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"balbir@linux.vnet.ibm.com" <balbir@linux.vnet.ibm.com>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>
Subject: Re: [bug][mmtom] memcg: MEM_CGROUP_ZSTAT underflow
Date: Fri, 19 Dec 2008 18:29:29 +0900 [thread overview]
Message-ID: <20081219182929.428380df.kamezawa.hiroyu@jp.fujitsu.com> (raw)
In-Reply-To: <20081219172903.7ca9b123.nishimura@mxp.nes.nec.co.jp>
On Fri, 19 Dec 2008 17:29:03 +0900
Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp> wrote:
> Hi.
>
> Current(I'm testing 2008-12-16-15-50 with some patches, though) memcg have
> MEM_CGROUP_ZSTAT underflow problem.
>
> How to reproduce:
> - make a directory, set mem.limit.
> - run some programs exceeding mem.limit.
> - make another directory, and all the tasks in old directory to new one.
> - New directory's "inactive_anon" in memory.stat underflows.
>
> From my investigation:
> - This problem seems to happen only when swapping anonymous pages. It seems
> not to happen about shmem.
> - After removing memcg-fix-swap-accounting-leak-v3.patch(and of course
> memcg-fix-swap-accounting-leak-doc-fix.patch), this problem doesn't happen.
>
> Thoughts?
>
Thanks, then we need v4 ...but it just because my memcg-synchronized-lru.patch's
assumption about SwapCache was broken or not sane.
It assumes pc->page_cgroup is not changed after added to LRU, but now, it changes
because it can be dropped from SwapCache and new pc->mem_cgroup can be assigned.
Maybe mem_cgroup_lru_fixup() isn't enough, now.
Then..could you try this ? I can't do test right now, sorry.
==
From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
As memcg-fix-swap-accounting-leak-v3.patch pointed out, SwapCache
can be not SwapCache before commit.
In this case,
- the page is completely uncharged.
- but still on Old LRU.
- pc->mem_cgroup is changed before it's removed from LRU.
For avoiding race, remove page_cgroup from old LRU before we call commit.
Signed-off-by: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
---
mm/memcontrol.c | 21 +++++++++++++++++++++
1 file changed, 21 insertions(+)
Index: mmotm-Dec-17/mm/memcontrol.c
===================================================================
--- mmotm-Dec-17.orig/mm/memcontrol.c
+++ mmotm-Dec-17/mm/memcontrol.c
@@ -1152,12 +1152,27 @@ int mem_cgroup_cache_charge_swapin(struc
void mem_cgroup_commit_charge_swapin(struct page *page, struct mem_cgroup *ptr)
{
struct page_cgroup *pc;
+ struct zone *zone;
if (mem_cgroup_disabled())
return;
if (!ptr)
return;
+
pc = lookup_page_cgroup(page);
+
+ zone = page_zone(page);
+ spin_lock(&zone->lru_lock);
+ if (!PageSwapCache(page) && !list_empty(&pc->lru)) {
+ /*
+ * We need to forget old LRU before modifying pc->mem_cgroup.
+ * This is necessary only when the page is already uncharged
+ * by delete_from_swap_cache().
+ * (Nothing happens when pc->mem_cgroup is NULL.)
+ */
+ mem_cgroup_del_lru(page);
+ }
+ spin_unlock(&zone->lru_lock);
__mem_cgroup_commit_charge(ptr, pc, MEM_CGROUP_CHARGE_TYPE_MAPPED);
/*
* Now swap is on-memory. This means this page may be
@@ -1246,6 +1261,12 @@ __mem_cgroup_uncharge_common(struct page
mem_cgroup_charge_statistics(mem, pc, false);
ClearPageCgroupUsed(pc);
+ /*
+ * Don't clear pc->mem_cgroup because del_from_lru() will see this.
+ * The fully unchaged page is assumed to be freed after us, so it's
+ * safe. When this page is reused before free, we have to be careful.
+ * (In SwapCache case...it can happen.)
+ */
mz = page_cgroup_zoneinfo(pc);
unlock_page_cgroup(pc);
>
> Thanks,
> Daisuke Nishimura.
>
> --
> 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>
>
--
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:[~2008-12-19 9:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-19 8:29 Daisuke Nishimura
2008-12-19 9:29 ` KAMEZAWA Hiroyuki [this message]
2008-12-19 9:40 ` KAMEZAWA Hiroyuki
2008-12-19 17:08 ` 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=20081219182929.428380df.kamezawa.hiroyu@jp.fujitsu.com \
--to=kamezawa.hiroyu@jp.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=balbir@linux.vnet.ibm.com \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nishimura@mxp.nes.nec.co.jp \
/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