Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758468Ab2JaQtA (ORCPT ); Wed, 31 Oct 2012 12:49:00 -0400 Received: from cantor2.suse.de ([195.135.220.15]:59940 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758067Ab2JaQs6 (ORCPT ); Wed, 31 Oct 2012 12:48:58 -0400 Date: Wed, 31 Oct 2012 17:48:55 +0100 From: Michal Hocko To: Tejun Heo Cc: lizefan@huawei.com, hannes@cmpxchg.org, bsingharora@gmail.com, kamezawa.hiroyu@jp.fujitsu.com, containers@lists.linux-foundation.org, cgroups@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 1/8] cgroup: kill cgroup_subsys->__DEPRECATED_clear_css_refs Message-ID: <20121031164855.GI22809@dhcp22.suse.cz> References: <1351657365-25055-1-git-send-email-tj@kernel.org> <1351657365-25055-2-git-send-email-tj@kernel.org> <20121031143751.GA22809@dhcp22.suse.cz> <20121031164123.GD2945@htj.dyndns.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20121031164123.GD2945@htj.dyndns.org> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1487 Lines: 34 On Wed 31-10-12 09:41:23, Tejun Heo wrote: > Hey, Michal. > > On Wed, Oct 31, 2012 at 03:37:51PM +0100, Michal Hocko wrote: > > > + for_each_subsys(cgrp->root, ss) > > > + if (ss->pre_destroy) > > > + WARN_ON_ONCE(ss->pre_destroy(cgrp)); > > > > Hmm, I am not sure I like this WARN_ON_ONCE. First it can happen for > > more than one controller and second we can just clear CGRP_WAIT_ON_RMDIR > > and return with EBUSY. The only possible failure at the moment is when a > > new task or a child group appear. > > I know it is not a big deal because it will disappear later in the > > series but it would be more readable IMO. > > The WARN_ON_ONCE() is just moved from the original > cgroup_call_pre_destroy(). We can add an error out there but that > makes future changes difficult. It's a chicken and egg problem. You > gotta break the loop somewhere. I do not think this is that hard. You can simply change the return path on pre_destroy error by BUG_ON in "cgroup: deactivate CSS's and mark cgroup dead before invoking ->pre_destroy()". There is no chicke&egg problem here because once the group is marked dead and css frozen then the existing callbacks cannot possibly fail. Or am I missing your point? -- Michal Hocko SUSE Labs -- 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/