archive mirror
 help / color / mirror / Atom feed
From: Hugh Dickins <>
To: Arjan van de Ven <>
Cc: Dave McCracken <>, Andrew Morton <>,
	Linux Kernel <>,
	Linux Memory Management <>
Subject: Re: [PATCH 1/1] Implement shared page tables
Date: Wed, 31 Aug 2005 14:42:38 +0100 (BST)	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Wed, 31 Aug 2005, Arjan van de Ven wrote:
> On Wed, 2005-08-31 at 12:44 +0100, Hugh Dickins wrote:
> > I was going to say, doesn't randomize_va_space take away the rest of
> > the point?  But no, it appears "randomize_va_space", as it currently
> > appears in mainline anyway, is somewhat an exaggeration: it just shifts
> > the stack a little, with no effect on the rest of the va space.
> it also randomizes mmaps

Ah, via PF_RANDOMIZE, yes, thanks: so long as certain conditions are
fulfilled - and my RLIM_INFINITY RLIMIT_STACK has been preventing it.

And mmaps include shmats: so unless the process specifies non-NULL
shmaddr to attach at, it'll choose a randomized address for that too
(subject to those various conditions).

Which is indeed a further disincentive against shared page tables.


  reply	other threads:[~2005-08-31 13:40 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-30 22:13 [PATCH 1/1] Implement shared page tables Dave McCracken
2005-08-31 11:44 ` Hugh Dickins
2005-08-31 11:51   ` Arjan van de Ven
2005-08-31 13:42     ` Hugh Dickins [this message]
2005-08-31 14:31       ` Martin J. Bligh
2005-08-31 14:41         ` Arjan van de Ven
2005-08-31 15:06         ` Hugh Dickins
2005-08-31 15:39           ` Martin J. Bligh
2005-08-31 16:40   ` Dave McCracken
2005-09-02  1:58 ` Chen, Kenneth W
2005-09-02 16:40   ` Dave McCracken
2005-09-02  4:26 ` Chen, Kenneth W

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \

* 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;
as well as URLs for NNTP newsgroup(s).