From: David Rientjes <rientjes@google.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Vladimir Davydov <vdavydov@parallels.com>,
mhocko@suse.cz, linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] memcg: fix mutex not unlocked on memcg_create_kmem_cache fail path
Date: Thu, 30 Jan 2014 14:39:51 -0800 (PST) [thread overview]
Message-ID: <alpine.DEB.2.02.1401301438500.12223@chino.kir.corp.google.com> (raw)
In-Reply-To: <20140130141538.a9e3977b5e7b76bdcf59a15f@linux-foundation.org>
On Thu, 30 Jan 2014, Andrew Morton wrote:
> > It always was.
>
> eh? kmem_cache_create_memcg()'s kstrdup() will allocate the minimum
> needed amount of memory.
>
Ah, good point. We could this incrementally on my patch:
diff --git a/mm/memcontrol.c b/mm/memcontrol.c
--- a/mm/memcontrol.c
+++ b/mm/memcontrol.c
@@ -637,6 +637,9 @@ int memcg_limited_groups_array_size;
* better kept as an internal representation in cgroup.c. In any case, the
* cgrp_id space is not getting any smaller, and we don't have to necessarily
* increase ours as well if it increases.
+ *
+ * Updates to MAX_SIZE should update the space for the memcg name in
+ * memcg_create_kmem_cache().
*/
#define MEMCG_CACHES_MIN_SIZE 4
#define MEMCG_CACHES_MAX_SIZE MEM_CGROUP_ID_MAX
@@ -3400,8 +3403,10 @@ void mem_cgroup_destroy_cache(struct kmem_cache *cachep)
static struct kmem_cache *memcg_create_kmem_cache(struct mem_cgroup *memcg,
struct kmem_cache *s)
{
- char *name = NULL;
struct kmem_cache *new;
+ const char *cgrp_name;
+ char *name = NULL;
+ size_t len;
BUG_ON(!memcg_can_account_kmem(memcg));
@@ -3409,9 +3414,22 @@ static struct kmem_cache *memcg_create_kmem_cache(struct mem_cgroup *memcg,
if (unlikely(!name))
return NULL;
+ /*
+ * Format of a memcg's kmem cache name:
+ * <cache-name>(<memcg-id>:<cgroup-name>)
+ */
+ len = strlen(s->name);
+ /* Space for parentheses, colon, terminator */
+ len += 4;
+ /* MEMCG_CACHES_MAX_SIZE is USHRT_MAX */
+ len += 5;
+ BUILD_BUG_ON(MEMCG_CACHES_MAX_SIZE > USHRT_MAX);
+
rcu_read_lock();
- snprintf(name, PATH_MAX, "%s(%d:%s)", s->name, memcg_cache_id(memcg),
- cgroup_name(memcg->css.cgroup));
+ cgrp_name = cgroup_name(memcg->css.cgroup);
+ len += strlen(cgrp_name);
+ snprintf(name, len, "%s(%d:%s)", s->name, memcg_cache_id(memcg),
+ cgrp_name);
rcu_read_unlock();
new = kmem_cache_create_memcg(memcg, name, s->object_size, s->align,
--
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-30 22:39 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-30 16:01 Vladimir Davydov
2014-01-30 21:01 ` Andrew Morton
2014-01-30 21:14 ` David Rientjes
2014-01-30 21:29 ` Andrew Morton
2014-01-30 21:38 ` David Rientjes
2014-01-30 21:50 ` Andrew Morton
2014-01-30 22:04 ` David Rientjes
2014-01-30 22:09 ` Andrew Morton
2014-01-30 22:13 ` David Rientjes
2014-01-30 22:15 ` Andrew Morton
2014-01-30 22:39 ` David Rientjes [this message]
2014-01-31 6:53 ` Vladimir Davydov
2014-01-31 10:42 ` David Rientjes
2014-01-31 11:29 ` Vladimir Davydov
2014-01-30 21:36 ` David Rientjes
2014-01-30 21:09 ` David Rientjes
2014-01-31 15:39 boxerapp
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=alpine.DEB.2.02.1401301438500.12223@chino.kir.corp.google.com \
--to=rientjes@google.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.cz \
--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