From: Chuck Ebbert <cebbert@redhat.com>
To: Jiri Kosina <jkosina@suse.cz>
Cc: Jakub Jelinek <jakub@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
Ingo Molnar <mingo@elte.hu>, Roland McGrath <roland@redhat.com>,
"H. Peter Anvin" <hpa@zytor.com>,
Ulrich Kunitz <kune@deine-taler.de>,
Bret Towe <magnade@gmail.com>,
linux-kernel@vger.kernel.org,
Arjan van de Ven <arjan@infradead.org>
Subject: Re: [PATCH] [RESEND] PIE executable randomization
Date: Wed, 15 Aug 2007 13:39:51 -0400 [thread overview]
Message-ID: <46C33A67.1020102@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0708142224540.29843@jikos.suse.cz>
On 08/14/2007 04:41 PM, Jiri Kosina wrote:
> (added Arjan to CC, as he has been working on the kernel part of the
> randomization previously)
>
> On Tue, 14 Aug 2007, Jakub Jelinek wrote:
>
>> If I'm reading the above hunk correctly, this means we will randomize
>> all PIEs and even all dynamic linkers invoked as executables on i?86 and
>> x86_64, and on the rest of arches we won't randomize at all, instead
>> load ET_DYN objects at ELF_ET_DYN_BASE address. But I don't see anything
>> i?86/x86_64 specific on this.
>
> Hi Jakub,
>
> actually, it is currently arch-specific, and that's because of different
> memory layouts on different archs.
>
> It turned out recently that PIE-compiled binaries on x86_64, that perform
> larger amount of brk-allocations (for example bash) will not work (but
> they will work on ?86). This is because currently on ?86 the memory layout
> is as follows:
But your patch is enabling randomization for x86_64, because CONFIG_X86
includes both 32 and 64 bit archs.
next prev parent reply other threads:[~2007-08-15 17:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-08 14:03 [PATCH] [RESEND] PIE executable randomization Jiri Kosina
2007-08-14 20:06 ` Jakub Jelinek
2007-08-14 20:41 ` Jiri Kosina
2007-08-14 23:21 ` Jiri Kosina
2007-08-15 16:48 ` Kees Cook
2007-08-15 17:39 ` Chuck Ebbert [this message]
2007-08-15 21:05 ` Jiri Kosina
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=46C33A67.1020102@redhat.com \
--to=cebbert@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=arjan@infradead.org \
--cc=hpa@zytor.com \
--cc=jakub@redhat.com \
--cc=jkosina@suse.cz \
--cc=kune@deine-taler.de \
--cc=linux-kernel@vger.kernel.org \
--cc=magnade@gmail.com \
--cc=mingo@elte.hu \
--cc=roland@redhat.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