From: Balbir Singh <balbir@linux.vnet.ibm.com>
To: nishimura@mxp.nes.nec.co.jp
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
YAMAMOTO Takashi <yamamoto@valinux.co.jp>,
Paul Menage <menage@google.com>, Li Zefan <lizf@cn.fujitsu.com>,
David Rientjes <rientjes@google.com>,
Pavel Emelianov <xemul@openvz.org>,
Dhaval Giani <dhaval@linux.vnet.ibm.com>,
d-nishimura@mtf.biglobe.ne.jp
Subject: Re: [BUGFIX][PATCH mmotm] memcg: fix for hierarchical reclaim
Date: Sat, 22 Nov 2008 19:33:39 +0530 [thread overview]
Message-ID: <4928113B.8090504@linux.vnet.ibm.com> (raw)
In-Reply-To: <20081122114446.42ddca46.d-nishimura@mtf.biglobe.ne.jp>
Daisuke Nishimura wrote:
> mem_cgroup_from_res_counter should handle both mem->res and mem->memsw.
> This bug leads to NULL pointer dereference BUG at mem_cgroup_calc_reclaim.
>
> Signed-off-by: Daisuke Nishimura <nishimura@mxp.nes.nec.co.jp>
Thanks for catching this, could you please point me to the steps to reproduce
the problem
> ---
> This is fix for memory-cgroup-hierarchical-reclaim-v4.patch.
>
> mm/memcontrol.c | 23 +++++++++--------------
> 1 files changed, 9 insertions(+), 14 deletions(-)
>
> diff --git a/mm/memcontrol.c b/mm/memcontrol.c
> index d177ed7..ac445cf 100644
> --- a/mm/memcontrol.c
> +++ b/mm/memcontrol.c
> @@ -468,11 +468,8 @@ unsigned long mem_cgroup_isolate_pages(unsigned long nr_to_scan,
> return nr_taken;
> }
>
> -static struct mem_cgroup *
> -mem_cgroup_from_res_counter(struct res_counter *counter)
> -{
> - return container_of(counter, struct mem_cgroup, res);
> -}
> +#define mem_cgroup_from_res_counter(counter, member) \
> + container_of(counter, struct mem_cgroup, member)
>
> /*
> * This routine finds the DFS walk successor. This routine should be
> @@ -665,18 +662,16 @@ static int __mem_cgroup_try_charge(struct mm_struct *mm,
> /* mem+swap counter fails */
> res_counter_uncharge(&mem->res, PAGE_SIZE);
> noswap = true;
> - }
> + mem_over_limit = mem_cgroup_from_res_counter(fail_res,
> + memsw);
> + } else
> + /* mem counter fails */
> + mem_over_limit = mem_cgroup_from_res_counter(fail_res,
> + res);
> +
> if (!(gfp_mask & __GFP_WAIT))
> goto nomem;
>
> - /*
> - * Is one of our ancestors over their limit?
> - */
> - if (fail_res)
> - mem_over_limit = mem_cgroup_from_res_counter(fail_res);
> - else
> - mem_over_limit = mem;
> -
> ret = mem_cgroup_hierarchical_reclaim(mem_over_limit, gfp_mask,
> noswap);
>
Seems reasonable, but I want to test it.
--
Balbir
--
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-11-22 14:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-22 2:44 Daisuke Nishimura
2008-11-22 14:03 ` Balbir Singh [this message]
2008-11-23 1:31 ` Daisuke Nishimura
2008-11-23 7:15 ` Balbir Singh
2008-11-23 9:44 ` [BUGFIX(resend)][PATCH " Daisuke Nishimura, 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=4928113B.8090504@linux.vnet.ibm.com \
--to=balbir@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=d-nishimura@mtf.biglobe.ne.jp \
--cc=dhaval@linux.vnet.ibm.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-mm@kvack.org \
--cc=lizf@cn.fujitsu.com \
--cc=menage@google.com \
--cc=nishimura@mxp.nes.nec.co.jp \
--cc=rientjes@google.com \
--cc=xemul@openvz.org \
--cc=yamamoto@valinux.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