From: Benjamin LaHaise <bcrl@kvack.org>
To: Andi Kleen <ak@suse.de>
Cc: Ray Bryant <raybry@mpdtxmail.amd.com>,
Dave McCracken <dmccr@us.ibm.com>, Robin Holt <holt@sgi.com>,
Hugh Dickins <hugh@veritas.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Linux Memory Management <linux-mm@kvack.org>
Subject: Re: [PATCH/RFC] Shared page tables
Date: Mon, 23 Jan 2006 20:23:31 -0500 [thread overview]
Message-ID: <20060124012331.GK1008@kvack.org> (raw)
In-Reply-To: <200601240210.04337.ak@suse.de>
On Tue, Jan 24, 2006 at 02:10:03AM +0100, Andi Kleen wrote:
> The randomization is not for cache coloring, but for security purposes
> (except for the old very small stack randomization that was used
> to avoid conflicts on HyperThreaded CPUs). I would be surprised if the
> mmap made much difference because it's page aligned and at least
> on x86 the L2 and larger caches are usually PI.
Actually, does this even affect executable segments? Iirc, prelinking
already results in executables being mapped at the same physical offset
across binaries in a given system. An strace seems to confirm that.
-ben
--
"Ladies and gentlemen, I'm sorry to interrupt, but the police are here
and they've asked us to stop the party." Don't Email: <dont@kvack.org>.
next prev parent reply other threads:[~2006-01-24 1:27 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-05 16:19 [PATCH/RFC] Shared page tables Dave McCracken
2006-01-07 12:25 ` Heiko Carstens
2006-01-07 18:09 ` Dave McCracken
2006-01-08 12:09 ` Heiko Carstens
2006-01-08 14:04 ` Dave McCracken
2006-01-13 5:15 ` Brian Twichell
2006-01-13 22:34 ` Ray Bryant
2006-01-17 4:50 ` Brian Twichell
2006-01-25 4:14 ` Brian Twichell
2006-01-13 15:18 ` Phillip Susi
2006-01-14 20:45 ` Brian Twichell
2006-01-17 23:53 ` Robin Holt
2006-01-18 0:17 ` Dave Hansen
2006-01-18 6:11 ` Dave McCracken
2006-01-18 1:27 ` Chen, Kenneth W
2006-01-18 3:32 ` Robin Holt
2006-01-23 23:58 ` Ray Bryant
2006-01-24 0:16 ` Ray Bryant
2006-01-24 0:39 ` Andi Kleen
2006-01-24 0:51 ` Dave McCracken
2006-01-24 1:11 ` Andi Kleen
2006-01-24 1:26 ` Dave McCracken
2006-01-24 0:53 ` Ray Bryant
2006-01-24 1:00 ` Dave McCracken
2006-01-24 1:10 ` Andi Kleen
2006-01-24 1:23 ` Benjamin LaHaise [this message]
2006-01-24 1:38 ` Andi Kleen
2006-01-24 7:08 ` Arjan van de Ven
2006-01-24 7:06 ` Arjan van de Ven
2006-01-24 7:18 ` Andi Kleen
2006-01-27 18:16 ` Martin Bligh
2006-02-01 9:49 ` Nick Piggin
2006-01-24 14:48 ` Dave McCracken
2006-01-24 14:56 ` Arjan van de Ven
2006-01-24 0:19 ` Dave McCracken
2006-01-24 0:46 ` Ray Bryant
2006-01-24 23:43 ` Ray Bryant
2006-01-24 23:50 ` Dave McCracken
2006-01-25 0:21 ` Ray Bryant
2006-01-25 22:48 ` Ray Bryant
2006-01-25 22:52 ` Dave McCracken
2006-01-26 0:16 ` Ray Bryant
2006-01-26 0:58 ` Ray Bryant
2006-01-26 4:06 ` Robin Holt
2006-01-20 21:24 ` Hugh Dickins
2006-01-20 21:54 ` Chen, Kenneth W
2006-01-23 17:39 ` Dave McCracken
2006-01-23 20:19 ` Benjamin LaHaise
2006-01-24 17:50 ` Hugh Dickins
2006-01-24 18:07 ` Dave McCracken
2006-01-24 18:20 ` Hugh Dickins
2006-01-27 22:50 ` Brian Twichell
2006-01-30 18:46 ` Ray Bryant
2006-01-31 18:47 ` Brian Twichell
2006-01-31 19:18 ` Dave McCracken
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=20060124012331.GK1008@kvack.org \
--to=bcrl@kvack.org \
--cc=ak@suse.de \
--cc=dmccr@us.ibm.com \
--cc=holt@sgi.com \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=raybry@mpdtxmail.amd.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox