Subject: Re: mlock into kernel module
From: Arjan van de Ven <arjan@infradead.org>
To: "sej.kernel" <sej.kernel@gmail.com>
Cc: linux-kernel@vger.kernel.org
In-Reply-To: <4464A819.2050706@gmail.com>
References: <4464A819.2050706@gmail.com>
Content-Type: text/plain
Date: Fri, 12 May 2006 20:44:48 +0200
Message-Id: <1147459488.3173.42.camel@laptopd505.fenrus.org>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 821
Lines: 22

On Fri, 2006-05-12 at 17:22 +0200, sej.kernel wrote:
> Hello,
> I need to use mlock and munlock function into a kernel module. How so
> I call this system call from my module ?

no it's a bug if you need to do that

> I need to do this because I must use mlock in my software, but I can't
> use root or suser to start it. So mlock alwaays fail.

that's an rlimit thing, just fix the rlimit on your system.

Also if you want to do this for pinning hardware at a physical address
you have a really wrong design (mlock is the wrong api) which also
includes a security hole btw
 

-
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/