From: Vladimir Davydov <vdavydov@parallels.com>
To: mhocko@suse.cz, akpm@linux-foundation.org
Cc: glommer@gmail.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, cgroups@vger.kernel.org, devel@openvz.org,
Johannes Weiner <hannes@cmpxchg.org>,
Balbir Singh <bsingharora@gmail.com>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Subject: [PATCH RESEND 05/11] memcg: fix possible NULL deref while traversing memcg_slab_caches list
Date: Mon, 6 Jan 2014 12:44:56 +0400 [thread overview]
Message-ID: <a50a6ead66e13ff257441a6d01e60185b4f9c1fe.1388996525.git.vdavydov@parallels.com> (raw)
In-Reply-To: <cover.1388996525.git.vdavydov@parallels.com>
All caches of the same memory cgroup are linked in the memcg_slab_caches
list via kmem_cache::memcg_params::list. This list is traversed, for
example, when we read memory.kmem.slabinfo. Since the list actually
consists of memcg_cache_params objects, we have to convert an element of
the list to a kmem_cache object using memcg_params_to_cache(), which
obtains the pointer to the cache from the memcg_params::memcg_caches
array of the corresponding root cache. That said the pointer to a
kmem_cache in its parent's memcg_params must be initialized before
adding the cache to the list, and cleared only after it has been
unlinked. Currently it is vice-versa, which can result in a NULL ptr
dereference while traversing the memcg_slab_caches list. This patch
restores the correct order.
Signed-off-by: Vladimir Davydov <vdavydov@parallels.com>
Cc: Michal Hocko <mhocko@suse.cz>
Cc: Glauber Costa <glommer@gmail.com>
Cc: Johannes Weiner <hannes@cmpxchg.org>
Cc: Balbir Singh <bsingharora@gmail.com>
Cc: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: Andrew Morton <akpm@linux-foundation.org>
---
mm/memcontrol.c | 25 ++++++++++++++++++-------
1 file changed, 18 insertions(+), 7 deletions(-)
diff --git a/mm/memcontrol.c b/mm/memcontrol.c
index 999e7d4..d918626 100644
--- a/mm/memcontrol.c
+++ b/mm/memcontrol.c
@@ -3234,9 +3234,6 @@ void memcg_register_cache(struct kmem_cache *s)
css_get(&memcg->css);
- mutex_lock(&memcg->slab_caches_mutex);
- list_add(&s->memcg_params->list, &memcg->memcg_slab_caches);
- mutex_unlock(&memcg->slab_caches_mutex);
/*
* Since readers won't lock (see cache_from_memcg_idx()), we need a
@@ -3245,7 +3242,16 @@ void memcg_register_cache(struct kmem_cache *s)
*/
smp_wmb();
+ /*
+ * Initialize the pointer to this cache in its parent's memcg_params
+ * before adding it to the memcg_slab_caches list, otherwise we can
+ * fail to convert memcg_params_to_cache() while traversing the list.
+ */
root->memcg_params->memcg_caches[id] = s;
+
+ mutex_lock(&memcg->slab_caches_mutex);
+ list_add(&s->memcg_params->list, &memcg->memcg_slab_caches);
+ mutex_unlock(&memcg->slab_caches_mutex);
}
void memcg_unregister_cache(struct kmem_cache *s)
@@ -3257,16 +3263,21 @@ void memcg_unregister_cache(struct kmem_cache *s)
if (is_root_cache(s))
return;
- memcg = s->memcg_params->memcg;
- id = memcg_cache_id(memcg);
-
root = s->memcg_params->root_cache;
- root->memcg_params->memcg_caches[id] = NULL;
+ memcg = s->memcg_params->memcg;
+ id = memcg_cache_id(memcg);
mutex_lock(&memcg->slab_caches_mutex);
list_del(&s->memcg_params->list);
mutex_unlock(&memcg->slab_caches_mutex);
+ /*
+ * Clear the pointer to this cache in its parent's memcg_params only
+ * after removing it from the memcg_slab_caches list, otherwise we can
+ * fail to convert memcg_params_to_cache() while traversing the list.
+ */
+ root->memcg_params->memcg_caches[id] = NULL;
+
css_put(&memcg->css);
}
--
1.7.10.4
--
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-01-06 8:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-06 8:44 [PATCH RESEND 00/11] kmemcg-fixes Vladimir Davydov
2014-01-06 8:44 ` [PATCH RESEND 01/11] slab: cleanup kmem_cache_create_memcg() error handling Vladimir Davydov
2014-01-06 8:44 ` [PATCH RESEND 02/11] memcg, slab: kmem_cache_create_memcg(): fix memleak on fail path Vladimir Davydov
2014-01-06 8:44 ` [PATCH RESEND 03/11] memcg, slab: cleanup memcg cache initialization/destruction Vladimir Davydov
2014-01-06 8:44 ` [PATCH RESEND 04/11] memcg, slab: fix barrier usage when accessing memcg_caches Vladimir Davydov
2014-01-06 8:44 ` Vladimir Davydov [this message]
2014-01-06 8:44 ` [PATCH RESEND 06/11] memcg, slab: fix races in per-memcg cache creation/destruction Vladimir Davydov
2014-01-06 8:44 ` [PATCH RESEND 07/11] memcg: get rid of kmem_cache_dup Vladimir Davydov
2014-01-06 8:44 ` [PATCH RESEND 08/11] slab: do not panic if we fail to create memcg cache Vladimir Davydov
2014-01-06 8:45 ` [PATCH RESEND 09/11] memcg, slab: RCU protect memcg_params for root caches Vladimir Davydov
2014-01-06 8:45 ` [PATCH RESEND 10/11] memcg: remove KMEM_ACCOUNTED_ACTIVATED flag Vladimir Davydov
2014-01-06 8:45 ` [PATCH RESEND 11/11] memcg: rework memcg_update_kmem_limit synchronization Vladimir Davydov
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=a50a6ead66e13ff257441a6d01e60185b4f9c1fe.1388996525.git.vdavydov@parallels.com \
--to=vdavydov@parallels.com \
--cc=akpm@linux-foundation.org \
--cc=bsingharora@gmail.com \
--cc=cgroups@vger.kernel.org \
--cc=devel@openvz.org \
--cc=glommer@gmail.com \
--cc=hannes@cmpxchg.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@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