Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755820AbYCMNwa (ORCPT ); Thu, 13 Mar 2008 09:52:30 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753321AbYCMNwW (ORCPT ); Thu, 13 Mar 2008 09:52:22 -0400 Received: from namei.org ([69.55.235.186]:39670 "EHLO us.intercode.com.au" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751907AbYCMNwV (ORCPT ); Thu, 13 Mar 2008 09:52:21 -0400 Date: Fri, 14 Mar 2008 00:50:51 +1100 (EST) From: James Morris X-X-Sender: jmorris@us.intercode.com.au To: "Serge E. Hallyn" cc: lkml , linux-security-module@vger.kernel.org, Greg KH , Stephen Smalley , Casey Schaufler , Pavel Emelianov Subject: Re: [RFC] cgroups: implement device whitelist lsm (v2) In-Reply-To: <20080313131818.GA9771@sergelap.austin.ibm.com> Message-ID: References: <20080313032749.GA13258@sergelap.austin.ibm.com> <20080313131818.GA9771@sergelap.austin.ibm.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 901 Lines: 22 On Thu, 13 Mar 2008, Serge E. Hallyn wrote: > That does make for a simpler implementation at this point, however if > any other such LSMs come along (as Casey seemed to think they would) the > end result could end up being horrible spaghetti code of dependencies > and interrelated configs. That can be addressed as the need arises. A basic tenet of kernel development is to avoid speculative infrastructure. > But OTOH we went years with no such changes, so that's probably not a > particularly practical concern unless someone can cite specific upcoming > examples. So if noone objects I'll try that approach. -- James Morris -- 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/