From: Li Zefan <lizefan@huawei.com>
To: Michal Hocko <mhocko@suse.cz>
Cc: 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>,
Glauber Costa <glommer@parallels.com>
Subject: Re: [PATCH] memcg: fix memcg_cache_name() to use cgroup_name()
Date: Fri, 22 Mar 2013 09:22:06 +0800 [thread overview]
Message-ID: <514BB23E.70908@huawei.com> (raw)
In-Reply-To: <20130321102257.GH6094@dhcp22.suse.cz>
On 2013/3/21 18:22, Michal Hocko wrote:
> On Thu 21-03-13 10:08:49, Michal Hocko wrote:
>> On Thu 21-03-13 09:22:21, Li Zefan wrote:
>>> As cgroup supports rename, it's unsafe to dereference dentry->d_name
>>> without proper vfs locks. Fix this by using cgroup_name().
>>>
>>> Signed-off-by: Li Zefan <lizefan@huawei.com>
>>> ---
>>>
>>> This patch depends on "cgroup: fix cgroup_path() vs rename() race",
>>> which has been queued for 3.10.
>>>
>>> ---
>>> mm/memcontrol.c | 15 +++++++--------
>>> 1 file changed, 7 insertions(+), 8 deletions(-)
>>>
>>> diff --git a/mm/memcontrol.c b/mm/memcontrol.c
>>> index 53b8201..72be5c9 100644
>>> --- a/mm/memcontrol.c
>>> +++ b/mm/memcontrol.c
>>> @@ -3217,17 +3217,16 @@ void mem_cgroup_destroy_cache(struct kmem_cache *cachep)
>>> static char *memcg_cache_name(struct mem_cgroup *memcg, struct kmem_cache *s)
>>> {
>>> char *name;
>>> - struct dentry *dentry;
>>> +
>>> + name = (char *)__get_free_page(GFP_TEMPORARY);
>>
>> Ouch. Can we use a static temporary buffer instead?
>
>> This is called from workqueue context so we do not have to be afraid
>> of the deep call chain.
>
> Bahh, I was thinking about two things at the same time and that is how
> it ends... I meant a temporary buffer on the stack. But a separate
> allocation sounds even easier.
>
Actually I don't care much about which way to take. Use on-stack buffer (if stack
usage is not a concern) or local static buffer (caller already held memcg_cache_mutex)
is simplest.
But why it's bad to allocate a page for temp use?
>> It is also not a hot path AFAICS.
>>
>> Even GFP_ATOMIC for kasprintf would be an improvement IMO.
>
> What about the following (not even compile tested because I do not have
> cgroup_name in my tree yet):
No, it won't compile. ;)
> ---
> diff --git a/mm/memcontrol.c b/mm/memcontrol.c
> index f608546..ede0382 100644
> --- a/mm/memcontrol.c
> +++ b/mm/memcontrol.c
> @@ -3370,13 +3370,18 @@ static char *memcg_cache_name(struct mem_cgroup *memcg, struct kmem_cache *s)
> struct dentry *dentry;
>
> rcu_read_lock();
> - dentry = rcu_dereference(memcg->css.cgroup->dentry);
> + name = kasprintf(GFP_ATOMIC, "%s(%d:%s)", s->name,
> + memcg_cache_id(memcg), cgroup_name(memcg->css.cgroup));
> rcu_read_unlock();
>
> - BUG_ON(dentry == NULL);
> -
> - name = kasprintf(GFP_KERNEL, "%s(%d:%s)", s->name,
> - memcg_cache_id(memcg), dentry->d_name.name);
> + if (!name) {
> + name = kmalloc(PAGE_SIZE, GFP_KERNEL);
> + rcu_read_lock();
> + name = snprintf(name, PAGE_SIZE, "%s(%d:%s)", s->name,
> + memcg_cache_id(memcg),
> + cgroup_name(memcg->css.cgroup));
> + rcu_read_unlock();
> + }
>
> return name;
> }
>
next prev parent reply other threads:[~2013-03-22 1:22 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-21 1:22 [PATCH] memcg: fix memcg_cache_name() to use cgroup_name() Li Zefan
2013-03-21 9:08 ` Michal Hocko
2013-03-21 10:22 ` Michal Hocko
2013-03-22 1:22 ` Li Zefan [this message]
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
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
-- strict thread matches above, loose matches on Subject: below --
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=514BB23E.70908@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