Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261594AbVAGUqH (ORCPT ); Fri, 7 Jan 2005 15:46:07 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261557AbVAGUqH (ORCPT ); Fri, 7 Jan 2005 15:46:07 -0500 Received: from viper.oldcity.dca.net ([216.158.38.4]:14489 "HELO viper.oldcity.dca.net") by vger.kernel.org with SMTP id S261594AbVAGUpe (ORCPT ); Fri, 7 Jan 2005 15:45:34 -0500 Subject: Re: [PATCH] [request for inclusion] Realtime LSM From: Lee Revell To: Matt Mackall Cc: "Jack O'Quin" , Alan Cox , Andreas Steinmetz , Chris Wright , Linux Kernel Mailing List , Andrew Morton , Ingo Molnar , LAD mailing list In-Reply-To: <20050107200245.GW2940@waste.org> References: <1104374603.9732.32.camel@krustophenia.net> <20050103140359.GA19976@infradead.org> <1104862614.8255.1.camel@krustophenia.net> <20050104182010.GA15254@infradead.org> <1104865034.8346.4.camel@krustophenia.net> <41DB4476.8080400@domdv.de> <1104898693.24187.162.camel@localhost.localdomain> <20050107011820.GC2995@waste.org> <87brc17pj6.fsf@sulphur.joq.us> <20050107200245.GW2940@waste.org> Content-Type: text/plain Date: Fri, 07 Jan 2005 15:45:26 -0500 Message-Id: <1105130727.20278.71.camel@krustophenia.net> Mime-Version: 1.0 X-Mailer: Evolution 2.0.3 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1377 Lines: 30 On Fri, 2005-01-07 at 12:02 -0800, Matt Mackall wrote: > The trouble with introducing something into the kernel is that once > done, it can't be undone. So you're absolutely going to meet > resistance to anything that can be a) done sufficiently in userspace > or b) can reasonably be done in a more generic manner so as to meet > the needs of a wider future audience. The onus is on the submitter to > meet these requirements because we can't easily kick out a broken API > after we accept it. For a big subsystem that exposes an API, you would be right. But this is a *really* simple problem, all you need is a way to tell it who gets RT privileges, which means uid or gid. So any future solution will be orthogonal to this one, and when users upgrade even a not very smart Perl script will be able to migrate the configuration. How many different ways are there to say "these are the non-root users who have realtime prvileges", anyway? Unless, of course, the solution that's eventually merged is *really* overcomplicated by comparison, in which case users will (rightly) reject it, and the system will have worked. Lee - 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/