From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Zan Lynx <zlynx@acm.org>
Cc: Jan-Benedict Glaw <jbglaw@lug-owl.de>,
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 19:48:20 +0000 [thread overview]
Message-ID: <1135021701.6051.42.camel@localhost.localdomain> (raw)
In-Reply-To: <1135017515.13318.11.camel@localhost>
On Llu, 2005-12-19 at 11:38 -0700, Zan Lynx wrote:
> How about clearing MCL_FUTURE on fork but allow exec to inherit it?
> That way a parent process could fork, mlockall in the child and exec a
> memlocked child. A regular fork,exec by a memlocked parent would not
> create a memlocked child.
>
> Seems less messy than a new flag, while keeping the benefits.
The behaviour of MCL_FUTURE is standards defined so we don't get to
change it. The behaviour of an added flag is up to us.
prev parent reply other threads:[~2005-12-19 19:48 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
2005-12-19 18:38 ` Zan Lynx
2005-12-19 19:48 ` Alan Cox [this message]
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=1135021701.6051.42.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 \
--cc=zlynx@acm.org \
/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