Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261439AbVAGOnR (ORCPT ); Fri, 7 Jan 2005 09:43:17 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261433AbVAGOnR (ORCPT ); Fri, 7 Jan 2005 09:43:17 -0500 Received: from mx1.redhat.com ([66.187.233.31]:1677 "EHLO mx1.redhat.com") by vger.kernel.org with ESMTP id S261439AbVAGOnI (ORCPT ); Fri, 7 Jan 2005 09:43:08 -0500 Date: Fri, 7 Jan 2005 15:42:23 +0100 From: Arjan van de Ven To: Paul Davis Cc: Christoph Hellwig , Lee Revell , Ingo Molnar , Chris Wright , Alan Cox , "Jack O'Quin" , Linux Kernel Mailing List , Andrew Morton Subject: Re: [PATCH] [request for inclusion] Realtime LSM Message-ID: <20050107144223.GA28466@devserv.devel.redhat.com> References: <20050107142637.GB20398@devserv.devel.redhat.com> <200501071438.j07EccJ0018170@localhost.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200501071438.j07EccJ0018170@localhost.localdomain> User-Agent: Mutt/1.4.1i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 842 Lines: 21 On Fri, Jan 07, 2005 at 09:38:38AM -0500, Paul Davis wrote: > >> rlimit_memlock limits the *amount* of memory that mlock() can be used > >> on, not whether mlock can be used. at least, thats my understanding of > >> the POSIX design for this. the man page and the source code for mlock > >> support make that reasonably clear. > > > >eh no. It defaults to zero, but if you increase it for a specific user, that > >user is allowed to mlock more. > > from mm/mlock.c:do_mlock() in 2.6.8: > > if (on && !capable(CAP_IPC_LOCK)) > return -EPERM; now try 2.6.9 ;) this deficiency got already fixed - 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/