From: Michal Hocko <mhocko@suse.cz>
To: Johannes Weiner <hannes@cmpxchg.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Vladimir Davydov <vdavydov@parallels.com>,
linux-mm@kvack.org, cgroups@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [patch 2/3] mm: memcontrol: pull the NULL check from __mem_cgroup_same_or_subtree()
Date: Fri, 24 Oct 2014 20:30:32 +0200 [thread overview]
Message-ID: <20141024183032.GB18956@dhcp22.suse.cz> (raw)
In-Reply-To: <1414158589-26094-2-git-send-email-hannes@cmpxchg.org>
On Fri 24-10-14 09:49:48, Johannes Weiner wrote:
> The NULL in mm_match_cgroup() comes from a possibly exiting mm->owner.
> It makes a lot more sense to check where it's looked up, rather than
> check for it in __mem_cgroup_same_or_subtree() where it's unexpected.
>
> No other callsite passes NULL to __mem_cgroup_same_or_subtree().
Much better!
> Signed-off-by: Johannes Weiner <hannes@cmpxchg.org>
Acked-by: Michal Hocko <mhocko@suse.cz>
> ---
> include/linux/memcontrol.h | 5 +++--
> mm/memcontrol.c | 2 +-
> 2 files changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/include/linux/memcontrol.h b/include/linux/memcontrol.h
> index ea007615e8f9..e32ab948f589 100644
> --- a/include/linux/memcontrol.h
> +++ b/include/linux/memcontrol.h
> @@ -83,11 +83,12 @@ static inline
> bool mm_match_cgroup(const struct mm_struct *mm, const struct mem_cgroup *memcg)
> {
> struct mem_cgroup *task_memcg;
> - bool match;
> + bool match = false;
>
> rcu_read_lock();
> task_memcg = mem_cgroup_from_task(rcu_dereference(mm->owner));
> - match = __mem_cgroup_same_or_subtree(memcg, task_memcg);
> + if (task_memcg)
> + match = __mem_cgroup_same_or_subtree(memcg, task_memcg);
> rcu_read_unlock();
> return match;
> }
> diff --git a/mm/memcontrol.c b/mm/memcontrol.c
> index bdf8520979cf..15b1c5110a8f 100644
> --- a/mm/memcontrol.c
> +++ b/mm/memcontrol.c
> @@ -1316,7 +1316,7 @@ bool __mem_cgroup_same_or_subtree(const struct mem_cgroup *root_memcg,
> {
> if (root_memcg == memcg)
> return true;
> - if (!root_memcg->use_hierarchy || !memcg)
> + if (!root_memcg->use_hierarchy)
> return false;
> return cgroup_is_descendant(memcg->css.cgroup, root_memcg->css.cgroup);
> }
> --
> 2.1.2
>
--
Michal Hocko
SUSE Labs
--
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:[~2014-10-24 18:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-24 13:49 [patch 1/3] mm: memcontrol: remove bogus NULL check after mem_cgroup_from_task() Johannes Weiner
2014-10-24 13:49 ` [patch 2/3] mm: memcontrol: pull the NULL check from __mem_cgroup_same_or_subtree() Johannes Weiner
2014-10-24 14:49 ` Vladimir Davydov
2014-10-24 18:30 ` Michal Hocko [this message]
2014-10-24 13:49 ` [patch 3/3] mm: memcontrol: drop bogus RCU locking from mem_cgroup_same_or_subtree() Johannes Weiner
2014-10-24 15:22 ` Vladimir Davydov
2014-10-24 18:41 ` Michal Hocko
2014-10-24 14:41 ` [patch 1/3] mm: memcontrol: remove bogus NULL check after mem_cgroup_from_task() Vladimir Davydov
2014-10-24 18:29 ` Michal Hocko
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=20141024183032.GB18956@dhcp22.suse.cz \
--to=mhocko@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=vdavydov@parallels.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