From: "H. Peter Anvin" <hpa@zytor.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: Jiri Kosina <jkosina@suse.cz>,
LKML <linux-kernel@vger.kernel.org>,
Josh Boyer <jwboyer@redhat.com>
Subject: Re: [PATCH] binfmt_elf: fix PIE load with randomization disabled
Date: Mon, 09 Dec 2013 14:01:51 -0800 [thread overview]
Message-ID: <52A63DCF.2060504@zytor.com> (raw)
In-Reply-To: <CAMe9rOqF5f2Wktsqf_43hwa_c20+_S+W8N5VDZ6TVqPXDh7puw@mail.gmail.com>
On 12/09/2013 01:59 PM, H.J. Lu wrote:
>
> A Linux/x86-64 user came to me at the end of 2008. He needed
> to load an executable above 4GB. I added -Ttext-segment option
> to linker:
>
> https://sourceware.org/ml/binutils/2009-01/msg00173.html
>
> so that he could load his program compiled as PIE above 4GB.
> If kernel is changed not to honor it, his program won't work any more.
> In normal case, PIE has zero vaddr and this doesn't apply.
>
That doesn't seem to be PIE at all, and if it is PIE, then it should be
relocatable (I agree btw with randomizing upward from the selected address.)
-hpa
next prev parent reply other threads:[~2013-12-09 22:02 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-09 15:50 H.J. Lu
2013-12-09 20:57 ` Jiri Kosina
2013-12-09 21:03 ` H.J. Lu
2013-12-09 21:13 ` Jiri Kosina
2013-12-09 21:47 ` H.J. Lu
2013-12-09 21:49 ` H. Peter Anvin
2013-12-09 21:52 ` H.J. Lu
2013-12-09 21:53 ` H. Peter Anvin
2013-12-09 21:59 ` H.J. Lu
2013-12-09 22:01 ` H. Peter Anvin [this message]
2013-12-09 22:03 ` H.J. Lu
2013-12-11 13:36 ` Jiri Kosina
2013-12-11 13:41 ` H.J. Lu
2013-12-11 17:49 ` H. Peter Anvin
2013-12-11 18:21 ` H.J. Lu
2013-12-11 19:43 ` H. Peter Anvin
2013-12-11 20:02 ` H.J. Lu
2013-12-09 21:51 ` Jiri Kosina
2013-12-09 21:39 ` H. Peter Anvin
2013-12-09 21:44 ` H.J. Lu
2013-12-09 23:35 ` H. Peter Anvin
2013-12-09 23:53 ` H.J. Lu
2013-12-10 0:37 ` H. Peter Anvin
2013-12-10 0:41 ` H.J. Lu
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=52A63DCF.2060504@zytor.com \
--to=hpa@zytor.com \
--cc=hjl.tools@gmail.com \
--cc=jkosina@suse.cz \
--cc=jwboyer@redhat.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®