From: Andrea Arcangeli <andrea@suse.de>
To: Rik van Riel <riel@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.5-rc1-aa1
Date: Sat, 20 Mar 2004 17:31:32 +0100 [thread overview]
Message-ID: <20040320163132.GV9009@dualathlon.random> (raw)
In-Reply-To: <Pine.LNX.4.44.0403181144290.16728-100000@chimarrao.boston.redhat.com>
On Thu, Mar 18, 2004 at 11:49:52AM -0500, Rik van Riel wrote:
> It's in the RHEL3 kernel, a patch named linux-2.4.21-mlock.patch.
>
> Basically it allows any normal process to have up to its
> current->rlim[RLIMIT_MEMLOCK].rlim_cur memory locked.
> Root can configure, in /etc/security/limits.conf, how much
> memory the processes of each user are allowed to mlock.
>
> Processes with CAP_IPC_LOCK set can mlock as much as they
> want, unrestricted by the limit.
>
> Last year at the kernel summit, Linus seemed pretty happy
> with this approach. I think Wim Coekaerts at Oracle has
> ported the patch to 2.6 already...
>
> I suspect the security paranoid will like this patch too,
> because it allows gnupg to mlock the memory it wants to
> have locked.
I agree.
> Now it just needs to be submitted to Andrew and Linus ;)
could somebody submit it to me too? ;) otherwise I'll have to search for
some big rpm.
what I was thinking about was more basic without checking the rlimits,
certainly I agree using the rlimits is a very nice bonus (though the
code is a bit more complicated, and it won't be a one liner in
remap_file_pages as I was hoping for ;).
next prev parent reply other threads:[~2004-03-20 16:30 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-18 2:22 2.6.5-rc1-aa1 Andrea Arcangeli
2004-03-18 15:32 ` 2.6.5-rc1-aa1 Rik van Riel
2004-03-18 15:53 ` 2.6.5-rc1-aa1 Andrea Arcangeli
2004-03-18 16:42 ` 2.6.5-rc1-aa1 Andrea Arcangeli
2004-03-18 16:49 ` 2.6.5-rc1-aa1 Rik van Riel
2004-03-18 20:15 ` 2.6.5-rc1-aa1 Diego Calleja García
2004-03-19 0:34 ` 2.6.5-rc1-aa1 Bill Davidsen
2004-03-19 1:51 ` 2.6.5-rc1-aa1 Diego Calleja García
2004-03-20 16:31 ` Andrea Arcangeli [this message]
2004-03-20 16:36 ` 2.6.5-rc1-aa1 Marc-Christian Petersen
2004-03-18 20:41 ` 2.6.5-rc1-aa1 Hugh Dickins
2004-03-18 23:06 ` 2.6.5-rc1-aa1 Andrea Arcangeli
2004-03-18 23:29 ` 2.6.5-rc1-aa1 Andrea Arcangeli
2004-03-19 0:49 ` 2.6.5-rc1-aa1 Paul Mackerras
2004-03-20 13:35 ` 2.6.5-rc1-aa1 Rik van Riel
2004-03-20 14:25 ` 2.6.5-rc1-aa1 Andrea Arcangeli
2004-03-18 22:14 ` 2.6.5-rc1-aa1 Andrea Arcangeli
2004-03-18 22:37 ` 2.6.5-rc1-aa1 Hugh Dickins
2004-03-18 23:09 ` 2.6.5-rc1-aa1 Andrea Arcangeli
[not found] <Pine.GSO.4.58.0403181228360.24039@blue.engin.umich.edu>
2004-03-18 18:03 ` 2.6.5-rc1-aa1 Rik van Riel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040320163132.GV9009@dualathlon.random \
--to=andrea@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.