From: Andrew Morton <akpm@linux-foundation.org>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: Michal Hocko <mhocko@suse.cz>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Miklos Szeredi <mszeredi@suse.cz>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
cgroups@vger.kernel.org,
"hannes@cmpxchg.org" <hannes@cmpxchg.org>,
Hugh Dickins <hughd@google.com>
Subject: Re: [BUGFIX][PATCH v2] add mem_cgroup_replace_page_cache.
Date: Fri, 9 Dec 2011 12:37:01 -0800 [thread overview]
Message-ID: <20111209123701.7e43dadf.akpm@linux-foundation.org> (raw)
In-Reply-To: <20111208161829.b6101de6.kamezawa.hiroyu@jp.fujitsu.com>
On Thu, 8 Dec 2011 16:18:29 +0900
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com> wrote:
> commit ef6a3c6311 adds a function replace_page_cache_page(). This
> function replaces a page in radix-tree with a new page.
> At doing this, memory cgroup need to fix up the accounting information.
> memcg need to check PCG_USED bit etc.
>
> In some(many?) case, 'newpage' is on LRU before calling replace_page_cache().
> So, memcg's LRU accounting information should be fixed, too.
>
> This patch adds mem_cgroup_replace_page_cache() and removing old hooks.
> In that function, old pages will be unaccounted without touching res_counter
> and new page will be accounted to the memcg (of old page). At overwriting
> pc->mem_cgroup of newpage, take zone->lru_lock and avoid race with
> LRU handling.
>
> Background:
> replace_page_cache_page() is called by FUSE code in its splice() handling.
> Here, 'newpage' is replacing oldpage but this newpage is not a newly allocated
> page and may be on LRU. LRU mis-accounting will be critical for memory cgroup
> because rmdir() checks the whole LRU is empty and there is no account leak.
> If a page is on the other LRU than it should be, rmdir() will fail.
>
> Changelog: v1 -> v2
> - fixed mem_cgroup_disabled() check missing.
> - added comments.
>
> Acked-by: Johannes Weiner <hannes@cmpxchg.org>
> Signed-off-by: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
> ---
> include/linux/memcontrol.h | 6 ++++++
> mm/filemap.c | 18 ++----------------
> mm/memcontrol.c | 44 ++++++++++++++++++++++++++++++++++++++++++++
> 3 files changed, 52 insertions(+), 16 deletions(-)
It's a relatively intrusive patch and I'm a bit concerned about
feeding it into 3.2.
How serious is the bug, and which kernel version(s) do you think we
should fix it in?
--
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 internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2011-12-09 20:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-06 3:39 [BUGFIX][PATCH] " KAMEZAWA Hiroyuki
2011-12-06 10:12 ` [RFC][PATCH 1/4] memcg: simplify page cache charging KAMEZAWA Hiroyuki
2011-12-06 10:13 ` [RFC][PATCH 2/4] memcg: simplify corner case handling of LRU and charge races KAMEZAWA Hiroyuki
2011-12-06 10:15 ` [RFC][PATCH 3/4] memcg: clear pc->mem_cgroup if necessary KAMEZAWA Hiroyuki
2011-12-06 10:17 ` [RFC][PATCH 4/4] memcg: new LRU rule KAMEZAWA Hiroyuki
2011-12-07 9:21 ` [BUGFIX][PATCH] add mem_cgroup_replace_page_cache Johannes Weiner
2011-12-07 11:14 ` Michal Hocko
2011-12-08 7:18 ` [BUGFIX][PATCH v2] " KAMEZAWA Hiroyuki
2011-12-08 9:31 ` Michal Hocko
2011-12-09 20:37 ` Andrew Morton [this message]
2011-12-12 0:48 ` 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=20111209123701.7e43dadf.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=hughd@google.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.cz \
--cc=mszeredi@suse.cz \
/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