Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758043AbYCNBld (ORCPT ); Thu, 13 Mar 2008 21:41:33 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754584AbYCNBlZ (ORCPT ); Thu, 13 Mar 2008 21:41:25 -0400 Received: from e35.co.us.ibm.com ([32.97.110.153]:44966 "EHLO e35.co.us.ibm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752694AbYCNBlY (ORCPT ); Thu, 13 Mar 2008 21:41:24 -0400 Date: Thu, 13 Mar 2008 20:41:21 -0500 From: "Serge E. Hallyn" To: James Morris Cc: "Serge E. Hallyn" , lkml , linux-security-module@vger.kernel.org, Greg KH , Stephen Smalley , Casey Schaufler , Pavel Emelianov Subject: Re: [RFC] cgroups: implement device whitelist lsm (v2) Message-ID: <20080314014121.GA8320@sergelap.austin.ibm.com> References: <20080313032749.GA13258@sergelap.austin.ibm.com> <20080313131818.GA9771@sergelap.austin.ibm.com> <20080313143803.GA11265@sergelap.austin.ibm.com> <20080313224616.GA9139@sergelap.austin.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.16 (2007-06-09) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1574 Lines: 46 Quoting James Morris (jmorris@namei.org): > On Thu, 13 Mar 2008, Serge E. Hallyn wrote: > > > Quoting James Morris (jmorris@namei.org): > > > On Thu, 13 Mar 2008, Serge E. Hallyn wrote: > > > > > > > True, but while this change simplifies the code a bit, the semantics > > > > seem more muddled - devcg will be enforcing when CONFIG_CGROUP_DEV=y > > > > and: > > > > > > > > SECURITY=n or > > > > rootplug is enabled > > > > capabilities is enabled > > > > smack is enabled > > > > selinux+capabilities is enabled > > > > > > Well, this is how real systems are going to be deployed. > > > > Sorry, do you mean with capabilities? > > Yes. > > All Fedora, RHEL, CentOS etc. ship with SELinux+capabilities. I can't > imagine not enabling them on other kernels. > > > > It becomes confusing, IMHO, if you have to change which secondary LSM you > > > stack with SELinux to enable a cgroup feature. > > > > So you're saying selinux without capabilities should still be able to > > use dev_cgroup? (Just making sure I understand right) > > Nope, SELinux always stacks with capabilities, so havng the cgroup hooks > in capabilities makes sense (rather than having us change the secondary > stacking LSM just to enable a feature). Oh, ok. Will let the patch stand until Pavel and Greg comment then. thanks, -serge -- 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/