From: Johannes Weiner <hannes@cmpxchg.org>
To: Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Balbir Singh <balbir@linux.vnet.ibm.com>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
LKML <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>
Subject: Re: [BUGFIX][PATCH] memcg: fix memory migration of shmem swapcache
Date: Wed, 5 Jan 2011 12:58:40 +0100 [thread overview]
Message-ID: <20110105115840.GD4654@cmpxchg.org> (raw)
In-Reply-To: <20110105130020.e2a854e4.nishimura@mxp.nes.nec.co.jp>
On Wed, Jan 05, 2011 at 01:00:20PM +0900, Daisuke Nishimura wrote:
> In current implimentation, mem_cgroup_end_migration() decides whether the page
> migration has succeeded or not by checking "oldpage->mapping".
>
> But if we are tring to migrate a shmem swapcache, the page->mapping of it is
> NULL from the begining, so the check would be invalid.
> As a result, mem_cgroup_end_migration() assumes the migration has succeeded
> even if it's not, so "newpage" would be freed while it's not uncharged.
>
> This patch fixes it by passing mem_cgroup_end_migration() the result of the
> page migration.
Are there other users that rely on unused->mapping being NULL after
migration?
If so, aren't they prone to misinterpreting this for shmem swapcache
as well?
If not, wouldn't it be better to remove that page->mapping = NULL from
migrate_page_copy() altogether? I think it's an ugly exception where
the outcome of PageAnon() is not meaningful for an LRU page.
To your patch:
> --- a/mm/memcontrol.c
> +++ b/mm/memcontrol.c
> @@ -2856,7 +2856,7 @@ int mem_cgroup_prepare_migration(struct page *page,
>
> /* remove redundant charge if migration failed*/
> void mem_cgroup_end_migration(struct mem_cgroup *mem,
> - struct page *oldpage, struct page *newpage)
> + struct page *oldpage, struct page *newpage, int result)
> {
> struct page *used, *unused;
> struct page_cgroup *pc;
> @@ -2865,8 +2865,7 @@ void mem_cgroup_end_migration(struct mem_cgroup *mem,
> return;
> /* blocks rmdir() */
> cgroup_exclude_rmdir(&mem->css);
> - /* at migration success, oldpage->mapping is NULL. */
> - if (oldpage->mapping) {
> + if (result) {
Since this function does not really need more than a boolean value,
wouldn't it make the code more obvious if the parameter was `bool
success'?
if (!success) {
> used = oldpage;
> unused = newpage;
> } else {
Minor nit, though. I agree with the patch in general.
Hannes
--
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:[~2011-01-05 11:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-05 4:00 Daisuke Nishimura
2011-01-05 4:48 ` Minchan Kim
2011-01-05 6:47 ` Daisuke Nishimura
2011-01-05 7:18 ` Minchan Kim
2011-01-06 0:52 ` KAMEZAWA Hiroyuki
2011-01-06 2:51 ` Minchan Kim
2011-01-05 11:58 ` Johannes Weiner [this message]
2011-01-06 1:09 ` Daisuke Nishimura
2011-01-06 1:55 ` KAMEZAWA Hiroyuki
2011-01-06 2:49 ` Minchan Kim
2011-01-06 3:34 ` [BUGFIX][PATCH v3] " Daisuke Nishimura
2011-01-06 5:42 ` Balbir Singh
2011-01-06 6:29 ` [BUGFIX][PATCH v4] " Daisuke Nishimura
2011-01-08 9:26 ` Johannes Weiner
2011-01-10 9:05 ` Balbir Singh
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=20110105115840.GD4654@cmpxchg.org \
--to=hannes@cmpxchg.org \
--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=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