[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <491A54EB.3020500@linux.vnet.ibm.com>
Date: Wed, 12 Nov 2008 09:30:43 +0530
From: Balbir Singh <balbir@...ux.vnet.ibm.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>
CC: linux-mm@...ck.org, YAMAMOTO Takashi <yamamoto@...inux.co.jp>,
Paul Menage <menage@...gle.com>, lizf@...fujitsu.com,
linux-kernel@...r.kernel.org,
Nick Piggin <nickpiggin@...oo.com.au>,
David Rientjes <rientjes@...gle.com>,
Pavel Emelianov <xemul@...nvz.org>,
Dhaval Giani <dhaval@...ux.vnet.ibm.com>,
Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [RFC][mm] [PATCH 3/4] Memory cgroup hierarchical reclaim (v3)
KAMEZAWA Hiroyuki wrote:
> On Tue, 11 Nov 2008 18:04:17 +0530
> Balbir Singh <balbir@...ux.vnet.ibm.com> wrote:
>
>> +
>> + /*
>> + * We need to give up the cgroup lock if it is held, since
>> + * it creates the potential for deadlock. cgroup_mutex should
>> + * be acquired after cpu_hotplug lock. In this path, we
>> + * acquire the cpu_hotplug lock after acquiring the cgroup_mutex
>> + * Giving it up should be OK
>> + */
>> + if (cgroup_locked)
>> + cgroup_unlock();
>
> nice catch. I'll post a fix to this as its own patch.
Sure, feel free to add my signed-off-by on it.
--
Balbir
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists