From: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
To: Andrea Righi <righi.andrea@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
balbir@linux.vnet.ibm.com,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"nishimura@mxp.nes.nec.co.jp" <nishimura@mxp.nes.nec.co.jp>
Subject: Re: [PATCH] memcg remove warning at DEBUG_VM=off
Date: Thu, 16 Apr 2009 09:47:38 +0900 [thread overview]
Message-ID: <20090416094738.2904c799.kamezawa.hiroyu@jp.fujitsu.com> (raw)
In-Reply-To: <20090415101317.GA3240@linux>
On Wed, 15 Apr 2009 12:13:17 +0200
Andrea Righi <righi.andrea@gmail.com> wrote:
> The warning is still there actually. I've just written a fix and seen
> this discussion, maybe I can offload a little bit Kame. ;)
>
> -Andrea
Thank you.
Reviewed-by: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
> ---
> memcg: remove warning when CONFIG_DEBUG_VM is not set
>
> Fix the following warning removing mem_cgroup_is_obsolete():
>
> mm/memcontrol.c:318: warning: ‘mem_cgroup_is_obsolete’ defined but not used
>
> Moreover, split the VM_BUG_ON() checks in two parts to be aware of which
> one triggered the bug.
>
> Signed-off-by: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
> Signed-off-by: Andrea Righi <righi.andrea@gmail.com>
> ---
> mm/memcontrol.c | 11 ++---------
> 1 files changed, 2 insertions(+), 9 deletions(-)
>
> diff --git a/mm/memcontrol.c b/mm/memcontrol.c
> index e44fb0f..8cd6358 100644
> --- a/mm/memcontrol.c
> +++ b/mm/memcontrol.c
> @@ -314,14 +314,6 @@ static struct mem_cgroup *try_get_mem_cgroup_from_mm(struct mm_struct *mm)
> return mem;
> }
>
> -static bool mem_cgroup_is_obsolete(struct mem_cgroup *mem)
> -{
> - if (!mem)
> - return true;
> - return css_is_removed(&mem->css);
> -}
> -
> -
> /*
> * Call callback function against all cgroup under hierarchy tree.
> */
> @@ -932,7 +924,8 @@ static int __mem_cgroup_try_charge(struct mm_struct *mm,
> if (unlikely(!mem))
> return 0;
>
> - VM_BUG_ON(!mem || mem_cgroup_is_obsolete(mem));
> + VM_BUG_ON(!mem);
> + VM_BUG_ON(css_is_removed(&mem->css));
>
> while (1) {
> int ret;
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
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-04-16 0:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-08 5:20 KAMEZAWA Hiroyuki
2009-04-08 5:27 ` Balbir Singh
2009-04-10 5:25 ` Andrew Morton
2009-04-10 6:33 ` KAMEZAWA Hiroyuki
2009-04-15 10:13 ` Andrea Righi
2009-04-16 0:47 ` KAMEZAWA Hiroyuki [this message]
2009-04-16 3:25 ` 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=20090416094738.2904c799.kamezawa.hiroyu@jp.fujitsu.com \
--to=kamezawa.hiroyu@jp.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=balbir@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nishimura@mxp.nes.nec.co.jp \
--cc=righi.andrea@gmail.com \
/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