Messages in this thread | | | Date | Fri, 7 Jan 2005 15:42:23 +0100 | From | Arjan van de Ven <> | Subject | Re: [PATCH] [request for inclusion] Realtime LSM |
| |
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/
| |