From: Glauber Costa <glommer@parallels.com>
To: Tejun Heo <tj@kernel.org>
Cc: Steffen Michalke <StMichalke@web.de>,
<linux-kernel@vger.kernel.org>, "Li Zefan" <lizefan@huawei.com>,
<containers@lists.linux-foundation.org>,
"Johannes Weiner" <hannes@cmpxchg.org>,
Michal Hocko <mhocko@suse.cz>,
Balbir Singh <bsingharora@gmail.com>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Subject: Re: PROBLEM: Crash cgdeleting empty memory cgroups with memory.kmem.limit_in_bytes set
Date: Thu, 21 Feb 2013 12:34:25 +0400 [thread overview]
Message-ID: <5125DC11.7060106@parallels.com> (raw)
In-Reply-To: <20130220230019.GJ3570@htj.dyndns.org>
On 02/21/2013 03:00 AM, Tejun Heo wrote:
> (cc'ing cgroup / memcg people and quoting whole body)
>
> Looks like something is going wrong with memcg cache destruction.
> Glauber, any ideas? Also, can we please not use names as generic as
> kmem_cache_destroy_work_func for something specific to memcg? How
> about something like memcg_destroy_cache_workfn?
>
I will take a look. Thanks for the report for the reportee: I tested
cgroup deletion quite extensively (quite important feature for me) so it
is nice to have an uncaught case.
About naming, I can change, no problem.
next prev parent reply other threads:[~2013-02-21 8:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-20 15:49 PROBLEM: Crash cgdeleting empty memory cgroups with memory.kmem.limit_in_bytes set Steffen Michalke
2013-02-20 23:00 ` Tejun Heo
2013-02-21 8:34 ` Glauber Costa [this message]
2013-02-22 3:15 ` Kamezawa Hiroyuki
2013-02-21 11:22 ` Glauber Costa
2013-02-21 15:44 ` 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=5125DC11.7060106@parallels.com \
--to=glommer@parallels.com \
--cc=StMichalke@web.de \
--cc=bsingharora@gmail.com \
--cc=containers@lists.linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizefan@huawei.com \
--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