From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Jan-Benedict Glaw <jbglaw@lug-owl.de>
Cc: Marc-Jano Knopp <pub_ml_lkml@marc-jano.de>,
Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org
Subject: Re: [Bug] mlockall() not working properly in 2.6.x
Date: Mon, 19 Dec 2005 17:47:30 +0000 [thread overview]
Message-ID: <1135014451.6051.23.camel@localhost.localdomain> (raw)
In-Reply-To: <20051219172735.GL13985@lug-owl.de>
On Llu, 2005-12-19 at 18:27 +0100, Jan-Benedict Glaw wrote:
> > > that we did this because inheriting MCL_FUTURE is standards-incorrect.
> >
> > Oh! So how can I make programs unswappable with kernel 2.6.x then?
>
> That would mean that you cannot just exec() another program that will
> also be mlockall()ed. The new program has to do that on its own...
mlockall MCL_FUTURE applies to this image only and the 2.6 behaviour is
correct if less useful in some ways. It would be possible to add an
inheriting MCL_ flag that was Linux specific but then how do you control
the depth of inheritance ? If that isn't an issue it looks the easiest.
Another possibility would be pmlockall(pid, flag), but that looks even
more nasty if it races an exec.
next prev parent reply other threads:[~2005-12-19 17:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-18 21:21 [Bug] mlockall() not working properly in 2.6.x Marc-Jano Knopp
2005-12-19 10:21 ` Andrew Morton
2005-12-19 11:42 ` Marc-Jano Knopp
2005-12-19 17:27 ` Jan-Benedict Glaw
2005-12-19 17:47 ` Alan Cox [this message]
2005-12-19 18:38 ` Zan Lynx
2005-12-19 19:48 ` Alan Cox
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=1135014451.6051.23.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=akpm@osdl.org \
--cc=jbglaw@lug-owl.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pub_ml_lkml@marc-jano.de \
/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.