From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Serge E. Hallyn" Subject: Re: [PATCH v6 9/9] devcg: propagate local changes down the hierarchy Date: Mon, 11 Feb 2013 18:52:39 +0000 Message-ID: <20130211185239.GA18779@mail.hallyn.com> References: <20130130171101.060853036@napanee.usersys.redhat.com> <20130130171102.390708521@napanee.usersys.redhat.com> <20130131043839.GA14726@mail.hallyn.com> <20130205183646.GT17632@redhat.com> <20130209040402.GA31942@mail.hallyn.com> <20130211143241.GF30962@redhat.com> <20130211174259.GA18179@mail.hallyn.com> <20130211183847.GG30962@redhat.com> Mime-Version: 1.0 Return-path: Content-Disposition: inline In-Reply-To: <20130211183847.GG30962@redhat.com> Sender: linux-kernel-owner@vger.kernel.org List-ID: Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Aristeu Rozanski Cc: "Serge E. Hallyn" , linux-kernel@vger.kernel.org, cgroups@vger.kernel.org, Tejun Heo , Serge Hallyn Quoting Aristeu Rozanski (aris@redhat.com): > On Mon, Feb 11, 2013 at 05:42:59PM +0000, Serge E. Hallyn wrote: > > Note I said only forbid behavior changes - not exception changes - to > > cgroups with children. > > that won't do much. behavior change is the simplest: if you change a > behavior, you wipe the local exceptions unless the special (deny, deny) > -> (allow, deny) case. Right but that is what has the most non-sensical implications for propagation. > exception propagation is harder But if we removed behavior change propagation, then your exception propagation not only would be correct, it could be simplified by removing the .local stuff altogether. Local would be obvious: if it's in current and not in parent, it's local. Or when adding a new exception e2, if exception e1 is in current and not in parent minus the new exception e2, then e1 is local. > getting rid of local settings would buy more simplicity (Not sure which you mean here by 'getting rid of local settings') -serge