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 13:38:56 -0800 (PST) [thread overview]
Message-ID: <alpine.DEB.2.02.1401301336530.15271@chino.kir.corp.google.com> (raw)
In-Reply-To: <20140130132939.96a25a37016a12f9a0093a90@linux-foundation.org>
On Thu, 30 Jan 2014, Andrew Morton wrote:
> > What's funnier is that tmp_name isn't required at all since
> > kmem_cache_create_memcg() is just going to do a kstrdup() on it anyway, so
> > you could easily just pass in the pointer to memory that has been
> > allocated for s->name rather than allocating memory twice.
>
> We need a buffer to sprintf() into.
>
Yeah, it shouldn't be temporary it should be the one and only allocation.
We should construct the name in memcg_create_kmem_cache() and be done with
it.
> diff -puN mm/memcontrol.c~mm-memcontrolc-memcg_create_kmem_cache-tweaks mm/memcontrol.c
> --- a/mm/memcontrol.c~mm-memcontrolc-memcg_create_kmem_cache-tweaks
> +++ a/mm/memcontrol.c
> @@ -3400,24 +3400,18 @@ void mem_cgroup_destroy_cache(struct kme
> static struct kmem_cache *memcg_create_kmem_cache(struct mem_cgroup *memcg,
> struct kmem_cache *s)
> {
> - struct kmem_cache *new = NULL;
> - static char *tmp_name = NULL;
> - static DEFINE_MUTEX(mutex); /* protects tmp_name */
> + struct kmem_cache *new;
> + char *tmp_name;
>
> BUG_ON(!memcg_can_account_kmem(memcg));
>
> - mutex_lock(&mutex);
> /*
> - * kmem_cache_create_memcg duplicates the given name and
> - * cgroup_name for this name requires RCU context.
> - * This static temporary buffer is used to prevent from
> - * pointless shortliving allocation.
> + * kmem_cache_create_memcg duplicates the given name and cgroup_name()
> + * for this name requires rcu_read_lock().
> */
> - if (!tmp_name) {
> - tmp_name = kmalloc(PATH_MAX, GFP_KERNEL);
> - if (!tmp_name)
> - goto out;
> - }
> + tmp_name = kmalloc(PATH_MAX, GFP_KERNEL);
> + if (!tmp_name)
> + return NULL;
>
> rcu_read_lock();
> snprintf(tmp_name, PATH_MAX, "%s(%d:%s)", s->name,
> @@ -3430,8 +3424,7 @@ static struct kmem_cache *memcg_create_k
> new->allocflags |= __GFP_KMEMCG;
> else
> new = s;
> -out:
> - mutex_unlock(&mutex);
> + kfree(tmp_name);
> return new;
> }
>
This is fine, but kmem_cache_create_memcg() is still just going to do a
pointless kstrdup() on it which isn't necessary.
--
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 21: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 [this message]
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
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.1401301336530.15271@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