From: Kees Cook <kees@outflux.net>
To: Hugh Dickins <hugh@veritas.com>
Cc: Andrew Morton <akpm@osdl.org>, Linus Torvalds <torvalds@osdl.org>,
Marcus Meissner <meissner@suse.de>, Andi Kleen <ak@suse.de>,
Ingo Molnar <mingo@elte.hu>, Dave Jones <davej@codemonkey.org.uk>,
Arjan van de Ven <arjan@linux.intel.com>,
linux-kernel@vger.kernel.org
Subject: Re: revert PIE randomization?
Date: Mon, 26 Mar 2007 13:17:43 -0700 [thread overview]
Message-ID: <20070326201743.GZ22797@outflux.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0703211940370.24602@blonde.wat.veritas.com>
On Wed, Mar 21, 2007 at 08:01:50PM +0000, Hugh Dickins wrote:
> It was in doing kernel builds that I hit it, nothing special: an
> overnight cycle of kernel building would collapse in a few hours.
> openSUSE 10.2.
I wonder it was the combination of the base addr randomization patch and
something specific to the openSuSE loader that was sparking the
failures? I ran about 22 million execs on Ubuntu Feisty (patched to
re-include the base addr randomization), with a PIE bash, and never saw
it. Hmpf.
> Andi would tell definitively, but I guess it's merely that with so
> much more address space to play with, x86_64 can divide up that space
> more satisfactorily.
>
> But don't be misled: try "ulimit -s unlimited" and I expect you'll
> find i386 allocating mmap addresses (hence libraries) from the
> opposite end, below ELF_ET_DYN_BASE.
Is there any explicitly documented per-arch "here is the memory layout
of a process"? I haven't been able to find anything like this. I
suspect it would be a good reference to have; so if no one has any
hints, I'll try to get something written up.
--
Kees Cook @outflux.net
prev parent reply other threads:[~2007-03-26 20:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-06 20:11 revert PIE randomization? Hugh Dickins
2007-01-06 21:04 ` Linus Torvalds
2007-01-06 21:08 ` Marcus Meissner
2007-01-06 21:45 ` Ingo Molnar
2007-01-06 21:54 ` Marcus Meissner
2007-01-06 22:42 ` David Woodhouse
2007-03-21 18:17 ` Kees Cook
2007-03-21 20:01 ` Hugh Dickins
2007-03-26 20:17 ` Kees Cook [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=20070326201743.GZ22797@outflux.net \
--to=kees@outflux.net \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=arjan@linux.intel.com \
--cc=davej@codemonkey.org.uk \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=meissner@suse.de \
--cc=mingo@elte.hu \
--cc=torvalds@osdl.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