From: Li Zefan <lizefan@huawei.com>
To: Michal Hocko <mhocko@suse.cz>
Cc: Glauber Costa <glommer@parallels.com>, Tejun Heo <tj@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Cgroups <cgroups@vger.kernel.org>,
linux-mm@kvack.org,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Johannes Weiner <hannes@cmpxchg.org>
Subject: Re: [PATCH] memcg: fix memcg_cache_name() to use cgroup_name()
Date: Sun, 24 Mar 2013 15:33:21 +0800 [thread overview]
Message-ID: <514EAC41.5050700@huawei.com> (raw)
In-Reply-To: <20130322093141.GE31457@dhcp22.suse.cz>
>> Thanks for identifying and fixing this.
>>
>> Li is right. The cache name will live long, but this is because the
>> slab/slub caches will strdup it internally. So the actual memcg
>> allocation is short lived.
>
> OK, I have totally missed that. Sorry about the confusion. Then all the
> churn around the allocation is pointless, no?
> What about:
> ---
>>From 7ed7f53bb597e8cb40d9ac91ce16142fb60f1e93 Mon Sep 17 00:00:00 2001
> From: Michal Hocko <mhocko@suse.cz>
> Date: Fri, 22 Mar 2013 10:22:54 +0100
> Subject: [PATCH] memcg: fix memcg_cache_name() to use cgroup_name()
>
> As cgroup supports rename, it's unsafe to dereference dentry->d_name
> without proper vfs locks. Fix this by using cgroup_name() rather than
> dentry directly.
>
> Also open code memcg_cache_name because it is called only from
> kmem_cache_dup which frees the returned name right after
> kmem_cache_create_memcg makes a copy of it. Such a short-lived
> allocation doesn't make too much sense. So replace it by a static
> buffer as kmem_cache_dup is called with memcg_cache_mutex.
>
I doubt it's a win to add 4K to kernel text size instead of adding
a few extra lines of code... but it's up to you.
> Signed-off-by: Li Zefan <lizefan@huawei.com>
> Signed-off-by: Michal Hocko <mhocko@suse.cz>
> ---
> mm/memcontrol.c | 33 +++++++++++----------------------
> 1 file changed, 11 insertions(+), 22 deletions(-)
...
> static struct kmem_cache *kmem_cache_dup(struct mem_cgroup *memcg,
> struct kmem_cache *s)
> {
> char *name;
> struct kmem_cache *new;
> + static char tmp_name[PAGE_SIZE];
>
> - name = memcg_cache_name(memcg, s);
> - if (!name)
> - return NULL;
> + lockdep_assert_held(&memcg_cache_mutex);
> +
> + rcu_read_lock();
> + tmp_name = snprintf(tmp_name, sizeof(tmp_name), "%s(%d:%s)", s->name,
> + memcg_cache_id(memcg), cgroup_name(memcg->css.cgroup));
I guess you didn't turn on CONFIG_MEMCG_KMEM?
snprintf() returns a int value.
> + rcu_read_unlock();
>
> - new = kmem_cache_create_memcg(memcg, name, s->object_size, s->align,
> + new = kmem_cache_create_memcg(memcg, tmp_name, s->object_size, s->align,
> (s->flags & ~SLAB_PANIC), s->ctor, s);
>
> if (new)
> new->allocflags |= __GFP_KMEMCG;
>
> - kfree(name);
> return new;
> }
>
>
--
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:[~2013-03-24 7:33 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-21 1:22 Li Zefan
2013-03-21 9:08 ` Michal Hocko
2013-03-21 10:22 ` Michal Hocko
2013-03-22 1:22 ` Li Zefan
2013-03-22 8:07 ` Michal Hocko
2013-03-22 8:17 ` Li Zefan
2013-03-22 8:22 ` Glauber Costa
2013-03-22 9:31 ` Michal Hocko
2013-03-22 9:41 ` Glauber Costa
2013-03-22 9:48 ` Michal Hocko
2013-03-22 10:03 ` Glauber Costa
2013-03-22 10:06 ` Michal Hocko
2013-03-22 10:25 ` Glauber Costa
2013-03-22 10:56 ` Michal Hocko
2013-03-24 7:34 ` Li Zefan
2013-03-25 8:20 ` Michal Hocko
2013-03-24 7:33 ` Li Zefan [this message]
2013-03-25 9:06 ` Michal Hocko
2013-03-26 7:52 ` Li Zefan
2013-03-26 8:10 ` Michal Hocko
2013-03-26 8:35 ` Glauber Costa
2013-03-26 8:43 ` Michal Hocko
2013-03-26 9:02 ` Glauber Costa
2013-03-27 1:15 ` Li Zefan
2013-03-27 8:37 ` Michal Hocko
2013-03-27 8:36 Michal Hocko
2013-03-27 14:58 ` Johannes Weiner
2013-03-27 15:11 ` Michal Hocko
2013-03-27 15:19 ` Glauber Costa
2013-03-27 15:32 ` Michal Hocko
2013-03-27 17:32 ` Michal Hocko
2013-03-28 7:48 ` Michal Hocko
2013-04-02 8:26 ` Michal Hocko
2013-04-03 21:33 ` Tejun Heo
2013-04-04 7:06 ` Michal Hocko
2013-03-27 15:32 ` Johannes Weiner
2013-03-27 15:47 ` Michal Hocko
2013-03-27 16:15 ` Tejun Heo
2013-03-27 16:19 ` Michal Hocko
2013-03-27 16:21 ` Tejun Heo
2013-03-27 16:27 ` Michal Hocko
2013-03-28 7:22 ` Glauber Costa
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=514EAC41.5050700@huawei.com \
--to=lizefan@huawei.com \
--cc=cgroups@vger.kernel.org \
--cc=glommer@parallels.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 \
--cc=tj@kernel.org \
/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