On 9/28/12 5:24 PM, Andrey Zonov wrote:
> On 9/27/12 7:25 PM, Simon L. B. Nielsen wrote:
>> On Tue, Sep 25, 2012 at 1:06 PM, Andrey Zonov wrote:
>>> Hi,
>>>
>>> Please review this patch [1] which allows unprivileged users call
>>> mlock()/munlock() and mlockall()/munlockall().
>>>
>>> AFAIK, these
On 9/27/12 7:25 PM, Simon L. B. Nielsen wrote:
> On Tue, Sep 25, 2012 at 1:06 PM, Andrey Zonov wrote:
>> Hi,
>>
>> Please review this patch [1] which allows unprivileged users call
>> mlock()/munlock() and mlockall()/munlockall().
>>
>> AFAIK, these calls were not allowed for every-one because acc
On Tue, Sep 25, 2012 at 1:06 PM, Andrey Zonov wrote:
> Hi,
>
> Please review this patch [1] which allows unprivileged users call
> mlock()/munlock() and mlockall()/munlockall().
>
> AFAIK, these calls were not allowed for every-one because accounting for
> mlockall(MCL_FUTURE) was not implemented.
Hi,
Please review this patch [1] which allows unprivileged users call
mlock()/munlock() and mlockall()/munlockall().
AFAIK, these calls were not allowed for every-one because accounting for
mlockall(MCL_FUTURE) was not implemented.
[1] http://people.freebsd.org/~zont/patches/mlock3.patch
--
An
on 28/08/2012 21:07 Bryan Drewery said the following:
> 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) fo