From owner-freebsd-arch@FreeBSD.ORG  Tue Aug 28 18:07:28 2012
Return-Path: <owner-freebsd-arch@FreeBSD.ORG>
Delivered-To: freebsd-arch@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id 189B31065673
	for <freebsd-arch@freebsd.org>; Tue, 28 Aug 2012 18:07:28 +0000 (UTC)
	(envelope-from bryan@shatow.net)
Received: from secure.xzibition.com (secure.xzibition.com [173.160.118.92])
	by mx1.freebsd.org (Postfix) with ESMTP id A16368FC1E
	for <freebsd-arch@freebsd.org>; Tue, 28 Aug 2012 18:07:27 +0000 (UTC)
DomainKey-Signature: a=rsa-sha1; c=nofws; d=shatow.net; h=message-id
	:date:from:mime-version:to:cc:subject:references:in-reply-to
	:content-type:content-transfer-encoding; q=dns; s=sweb; b=Foat9a
	+CRgsdxyU3CsjMlpQl14M4lY0G+NI7aXJ3vHrkrBFe95OJog3SgmuOjbzmEq6KZZ
	Z9B0AHvu8xQEEybuuf4JumnKSKFYX2rxGRyA+2WBJVsverL37+f4daGzjcog0XZp
	nxkwYgSCmPCkh6t5o2vBl6p9Q6v2lc9RIqw/s=
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=shatow.net; h=message-id
	:date:from:mime-version:to:cc:subject:references:in-reply-to
	:content-type:content-transfer-encoding; s=sweb; bh=Th7Q3+Bn+TfM
	5Ct9eEj8Nh58yZTpstCrxTea3gju8wQ=; b=O6XOYzMRMUjppBFzmFzSbgCDKe04
	yUNN/d7EP3jHRKhwkyrte861nmF0+6eAFGmElfrSQUDWKb3Yo6ZR+OjFZ++CMMp8
	Jg/+VSF/Ox4UQizcYu2WODN0IECuZy1DNVcEl18enJNwoCuv8GYWRmtPuiq8hr3I
	DziR7CCCMKfBFLE=
Received: (qmail 96059 invoked from network); 28 Aug 2012 13:07:20 -0500
Received: from unknown (HELO ?192.168.0.74?) (bryan@shatow.net@74.94.87.209)
	by sweb.xzibition.com with ESMTPA; 28 Aug 2012 13:07:20 -0500
Message-ID: <503D08D6.1040004@shatow.net>
Date: Tue, 28 Aug 2012 13:07:18 -0500
From: Bryan Drewery <bryan@shatow.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64;
	rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: Andrey Zonov <zont@FreeBSD.org>
References: <503CF3B1.3050604@FreeBSD.org>
In-Reply-To: <503CF3B1.3050604@FreeBSD.org>
X-Enigmail-Version: 1.4.3
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Cc: freebsd-arch@freebsd.org
Subject: Re: [patch] unprivileged mlock(2)
X-BeenThere: freebsd-arch@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Discussion related to FreeBSD architecture <freebsd-arch.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arch>
List-Post: <mailto:freebsd-arch@freebsd.org>
List-Help: <mailto:freebsd-arch-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
	<mailto:freebsd-arch-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Aug 2012 18:07:28 -0000

On 8/28/2012 11:37 AM, Andrey Zonov wrote:
> Hi,
> 
> We've got RLIMIT_MEMLOCK for years, but this limit is useless, because
> only root may call mlock(2), and root may raise any limits.
> 
> I suggest patch that allows to call mlock(2) for unprivileged users.
> Are there any objections to got it in tree?
> 

FYI, see previous recent thread on this here:

http://lists.freebsd.org/pipermail/freebsd-arch/2012-May/012552.html
and
http://lists.freebsd.org/pipermail/freebsd-arch/2012-June/012606.html

Bryan