Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759288Ab2JSURn (ORCPT ); Fri, 19 Oct 2012 16:17:43 -0400 Received: from mail-pa0-f46.google.com ([209.85.220.46]:53644 "EHLO mail-pa0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755086Ab2JSURl (ORCPT ); Fri, 19 Oct 2012 16:17:41 -0400 Date: Fri, 19 Oct 2012 13:17:36 -0700 From: Tejun Heo To: Li Zefan Cc: Michal Hocko , linux-mm@kvack.org, cgroups@vger.kernel.org, linux-kernel@vger.kernel.org, Johannes Weiner , KAMEZAWA Hiroyuki , Balbir Singh Subject: Re: [PATCH 4/6] cgroups: forbid pre_destroy callback to fail Message-ID: <20121019201736.GQ13370@google.com> References: <1350480648-10905-1-git-send-email-mhocko@suse.cz> <1350480648-10905-5-git-send-email-mhocko@suse.cz> <50811E5E.1090205@huawei.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <50811E5E.1090205@huawei.com> User-Agent: Mutt/1.5.20 (2009-06-14) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 975 Lines: 25 On Fri, Oct 19, 2012 at 05:33:18PM +0800, Li Zefan wrote: > On 2012/10/17 21:30, Michal Hocko wrote: > > Now that mem_cgroup_pre_destroy callback doesn't fail finally we can > > safely move on and forbit all the callbacks to fail. The last missing > > piece is moving cgroup_call_pre_destroy after cgroup_clear_css_refs so > > that css_tryget fails so no new charges for the memcg can happen. > > > The callbacks are also called from within cgroup_lock to guarantee that > > no new tasks show up. > > I'm afraid this won't work. See commit 3fa59dfbc3b223f02c26593be69ce6fc9a940405 > ("cgroup: fix potential deadlock in pre_destroy") Yeah, you're right. Argh... we really should unexport cgroup_lock soon. Thanks. -- tejun -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/