public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan-Benedict Glaw <jbglaw@lug-owl.de>
To: Marc-Jano Knopp <pub_ml_lkml@marc-jano.de>
Cc: 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 18:27:35 +0100	[thread overview]
Message-ID: <20051219172735.GL13985@lug-owl.de> (raw)
In-Reply-To: <20051219114231.GA2830@mjk.myfqdn.de>

[-- Attachment #1: Type: text/plain, Size: 1402 bytes --]

On Mon, 2005-12-19 12:42:31 +0100, Marc-Jano Knopp <pub_ml_lkml@marc-jano.de> wrote:
> On Mon, 19 Dec 2005 at 02:21 (-0800), Andrew Morton wrote:
> > Marc-Jano Knopp <pub_ml_lkml@marc-jano.de> wrote:
> > > A year ago, I wrote a small mlockall()-wrapper ("noswap") to make
> > > certain programs unswappable. It used to work perfectly, until I
> > > upgraded to kernel 2.6.x (2.6.13.1 in my case, but that shouldn't
> > > matter), which made the mlockall() execute without error, but also
> > > without any effect (the "L" in the STAT column of "ps axf" which
> > > indicates locked pages is missing).
> > Prior to 2.4.18 the kernel would allow MCL_FUTURE to propagate into child
> > processes.  But that was disabled in 2.4.18 and later.  I seem to recall
> > 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...

MfG, JBG

-- 
Jan-Benedict Glaw       jbglaw@lug-owl.de    . +49-172-7608481             _ O _
"Eine Freie Meinung in  einem Freien Kopf    | Gegen Zensur | Gegen Krieg  _ _ O
 für einen Freien Staat voll Freier Bürger"  | im Internet! |   im Irak!   O O O
ret = do_actions((curr | FREE_SPEECH) & ~(NEW_COPYRIGHT_LAW | DRM | TCPA));

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2005-12-19 17:27 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 [this message]
2005-12-19 17:47       ` Alan Cox
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=20051219172735.GL13985@lug-owl.de \
    --to=jbglaw@lug-owl.de \
    --cc=akpm@osdl.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox