From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261234AbUEKCAH (ORCPT ); Mon, 10 May 2004 22:00:07 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261405AbUEKCAH (ORCPT ); Mon, 10 May 2004 22:00:07 -0400 Received: from waste.org ([209.173.204.2]:9354 "EHLO waste.org") by vger.kernel.org with ESMTP id S261234AbUEKCAB (ORCPT ); Mon, 10 May 2004 22:00:01 -0400 Date: Mon, 10 May 2004 20:59:51 -0500 From: Matt Mackall To: Chris Wright Cc: Chris Wedgwood , Andrew Morton , Christoph Hellwig , linux-kernel@vger.kernel.org Subject: Re: 2.6.6-mm1 Message-ID: <20040511015951.GO5414@waste.org> References: <20040510024506.1a9023b6.akpm@osdl.org> <20040510223755.A7773@infradead.org> <20040510150203.3257ccac.akpm@osdl.org> <20040510231146.GA5168@taniwha.stupidest.org> <20040510163317.Y22989@build.pdx.osdl.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040510163317.Y22989@build.pdx.osdl.net> User-Agent: Mutt/1.3.28i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Mon, May 10, 2004 at 04:33:17PM -0700, Chris Wright wrote: > * Chris Wedgwood (cw@f00f.org) wrote: > > On Mon, May 10, 2004 at 03:02:03PM -0700, Andrew Morton wrote: > > > > > Capabilities are broken and don't work. Nobody has a clue how to > > > provide the required services with SELinux and nobody has any code > > > and we need the feature *now* before vendors go shipping even more > > > ghastly stuff. > > > > eh? magic groups are nasty... and why is this needed? can't > > oracle/whatever just run with a wrapper to give the capabilities out > > as required until a better solution is available > > I agree. I have a patch that at least fixes this bit of capabilities > (currently, what you suggest doesn't work right), which could easily be > dusted off and resent. > > And while we're at it, it would be nice to have the working bits of > memlock rlimits going. At least the mlock() users would get some help > (i.e. gpg). mlock() rlimits make sense independent of Oracle. There are a number of things (realtime, security, iscsi) that might make good use of small amounts of locked memory. > Another bit I could resend (removing the broken shm bits, > of course). It's just those pesky shm segs having their own lifecycle > which breaks the hugetlb and SHM_LOCK attempts to use memlock rlimits. They have a lifecycle like files (they live on a filesystem, after all), which is why I suggest we need quota there. Again, something that has sensible uses independent of Oracle. -- Matt Mackall : http://www.selenic.com : Linux development and consulting