Subject: Re: [PATCH v5 1/2] Always free struct memcg through schedule_work()

From: KAMEZAWA Hiroyuki <[email-masked]>
Date: Mon, 14 May 2012 09:56:20 +0900

(2012/05/12 5:11), Glauber Costa wrote:

> Right now we free struct memcg with kfree right after a
> rcu grace period, but defer it if we need to use vfree() to get
> rid of that memory area. We do that by need, because we need vfree
> to be called in a process context.
> 
> This patch unifies this behavior, by ensuring that even kfree will
> happen in a separate thread. The goal is to have a stable place to
> call the upcoming jump label destruction function outside the realm
> of the complicated and quite far-reaching cgroup lock (that can't be
> held when calling neither the cpu_hotplug.lock nor the jump_label_mutex)
> 
> Signed-off-by: Glauber Costa <[email-masked]>
> CC: Tejun Heo <[email-masked]>
> CC: Li Zefan <[email-masked]>
> CC: Kamezawa Hiroyuki <[email-masked]>
> CC: Johannes Weiner <[email-masked]>
> CC: Michal Hocko <[email-masked]>

I think we'll need to revisit this, again.
for now,
Acked-by: KAMEZAWA Hiroyuki <[email-masked]>