linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Glauber Costa <glommer@parallels.com>
To: Michal Hocko <mhocko@suse.cz>
Cc: Li Zefan <lizefan@huawei.com>,
	Johannes Weiner <hannes@cmpxchg.org>,
	KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Cgroups <cgroups@vger.kernel.org>,
	linux-mm@kvack.org
Subject: Re: [PATCH -v2] memcg: don't do cleanup manually if mem_cgroup_css_online() fails
Date: Wed, 3 Apr 2013 12:08:43 +0400	[thread overview]
Message-ID: <515BE38B.2060602@parallels.com> (raw)
In-Reply-To: <20130402150422.GB32520@dhcp22.suse.cz>

On 04/02/2013 07:04 PM, Michal Hocko wrote:
> On Tue 02-04-13 18:33:30, Glauber Costa wrote:
>> On 04/02/2013 06:28 PM, Michal Hocko wrote:
>>> On Tue 02-04-13 18:20:56, Glauber Costa wrote:
>>>> On 04/02/2013 06:16 PM, Michal Hocko wrote:
>>>>>  mem_cgroup_css_online
>>>>>       memcg_init_kmem
>>>>>         mem_cgroup_get		# refcnt = 2
>>>>>           memcg_update_all_caches
>>>>>             memcg_update_cache_size	# fails with ENOMEM
>>>>
>>>> Here is the thing: this one in kmem only happens for kmem enabled
>>>> memcgs. For those, we tend to do a get once, and put only when the last
>>>> kmem reference is gone.
>>>>
>>>> For non-kmem memcgs, refcnt will be 1 here, and will be balanced out by
>>>> the mem_cgroup_put() in css_free.
>>>
>>> So we need this, right?
>>> ---
>>> diff --git a/mm/memcontrol.c b/mm/memcontrol.c
>>> index f608546..2ef875d 100644
>>> --- a/mm/memcontrol.c
>>> +++ b/mm/memcontrol.c
>>> @@ -5306,6 +5306,8 @@ static int memcg_propagate_kmem(struct mem_cgroup *memcg)
>>>  	ret = memcg_update_cache_sizes(memcg);
>>>  	mutex_unlock(&set_limit_mutex);
>>>  out:
>>> +	if (ret)
>>> +		mem_cgroup_put(memcg);
>>>  	return ret;
>>>  }
>>>  #endif /* CONFIG_MEMCG_KMEM */
>>> @@ -6417,16 +6419,6 @@ mem_cgroup_css_online(struct cgroup *cont)
>>>  
>>>  	error = memcg_init_kmem(memcg, &mem_cgroup_subsys);
>>>  	mutex_unlock(&memcg_create_mutex);
>>> -	if (error) {
>>> -		/*
>>> -		 * We call put now because our (and parent's) refcnts
>>> -		 * are already in place. mem_cgroup_put() will internally
>>> -		 * call __mem_cgroup_free, so return directly
>>> -		 */
>>> -		mem_cgroup_put(memcg);
>>> -		if (parent->use_hierarchy)
>>> -			mem_cgroup_put(parent);
>>> -	}
>>>  	return error;
>>>  }
>>>  
>>>
>> Yes, indeed you are very right - and thanks for looking at such depth.
> 
> So what about the patch bellow? It seems that I provoked all this mess
> but my brain managed to push it away so I do not remember why I thought
> the parent needs reference drop... It is "only" 3.9 thing fortunately.
> ---

Li being fine with it, I am fine with it.

--
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>

      parent reply	other threads:[~2013-04-03  8:08 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-02  7:35 [PATCH] " Li Zefan
2013-04-02  8:03 ` Li Zefan
2013-04-02  8:07   ` Glauber Costa
2013-04-02  8:34     ` Li Zefan
2013-04-02  8:42       ` Glauber Costa
2013-04-02  8:43 ` Glauber Costa
2013-04-02 12:16 ` Michal Hocko
2013-04-02 12:22   ` Glauber Costa
2013-04-02 13:32     ` Michal Hocko
2013-04-02 13:36       ` Glauber Costa
2013-04-03  3:43       ` Li Zefan
2013-04-02 14:16   ` Michal Hocko
2013-04-02 14:20     ` Glauber Costa
2013-04-02 14:28       ` Michal Hocko
2013-04-02 14:33         ` Glauber Costa
2013-04-02 15:04           ` [PATCH -v2] " Michal Hocko
2013-04-03  3:49             ` Li Zefan
2013-04-03  7:43               ` Michal Hocko
2013-04-03  7:49                 ` Li Zefan
2013-04-03  8:18                   ` Michal Hocko
2013-04-03  8:30                     ` Glauber Costa
2013-04-03  8:37                     ` Li Zefan
2013-04-03  8:50                       ` Michal Hocko
2013-04-03  8:53                         ` [PATCH 1/2] Revert "memcg: avoid dangling reference count in creation failure." Michal Hocko
2013-04-03  8:53                           ` [PATCH 2/2] memcg, kmem: clean up reference count handling on the error path Michal Hocko
2013-04-03  9:48                             ` Michal Hocko
2013-04-03  8:08             ` Glauber Costa [this message]

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=515BE38B.2060602@parallels.com \
    --to=glommer@parallels.com \
    --cc=cgroups@vger.kernel.org \
    --cc=hannes@cmpxchg.org \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lizefan@huawei.com \
    --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