From: Ulrich Kunitz <kune@deine-taler.de>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Sergey Vlasov <vsu@altlinux.ru>,
Chuck Ebbert <cebbert@redhat.com>,
linux-kernel@vger.kernel.org, honza@jikos.cz, jkosina@suse.cz
Subject: Re: Is PIE randomization breaking klibc binaries?
Date: Thu, 2 Aug 2007 22:42:16 +0200 [thread overview]
Message-ID: <20070802204216.GA10311@deine-taler.de> (raw)
In-Reply-To: <46B22C25.2070601@zytor.com>
H. Peter Anvin wrote:
> Yup... it should probably be pointed out the reason the old kernel
> worked was nothing but pure dumb luck. This was a GNU ld change which
> needed to be undone for klibc. It's unfortunate that stock x86-64
> binaries leave as little of a null pointer range as they do, but that's
> life, unfortunately. The other alternative is to map klibc just below
> the 2 GB point, which would also work, but the old way broke when the ld
> change went in. As previously stated, klibc-1.4.35 or higher fixes this.
>
> -hpa
Just for the record: The kernel with the PIE patch boots perfectly
using the klibc 1.5 shared binaries on my machine.
--
Uli Kunitz
next prev parent reply other threads:[~2007-08-02 20:42 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-20 21:13 Ulrich Kunitz
2007-07-20 22:05 ` H. Peter Anvin
2007-07-24 20:34 ` Chuck Ebbert
2007-07-24 20:57 ` Chuck Ebbert
2007-07-24 22:00 ` Ulrich Kunitz
2007-07-24 22:41 ` Chuck Ebbert
2007-07-24 22:45 ` H. Peter Anvin
2007-07-24 23:13 ` Ulrich Kunitz
2007-07-25 6:32 ` Ulrich Kunitz
2007-07-31 11:30 ` Jiri Kosina
2007-07-31 12:01 ` H. Peter Anvin
2007-07-31 12:19 ` Jiri Kosina
2007-07-31 12:15 ` H. Peter Anvin
2007-08-01 14:07 ` Jiri Kosina
2007-08-02 4:29 ` Ulrich Kunitz
2007-08-02 11:21 ` Jiri Kosina
2007-08-02 17:03 ` Bret Towe
2007-08-02 19:02 ` Sergey Vlasov
2007-08-02 19:10 ` H. Peter Anvin
2007-08-02 20:42 ` Ulrich Kunitz [this message]
2007-08-02 21:03 ` Jiri Kosina
2007-08-02 19:10 ` Ulrich Kunitz
2007-07-21 6:02 ` Bret Towe
2007-07-21 10:18 ` Andrew Morton
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=20070802204216.GA10311@deine-taler.de \
--to=kune@deine-taler.de \
--cc=cebbert@redhat.com \
--cc=honza@jikos.cz \
--cc=hpa@zytor.com \
--cc=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=vsu@altlinux.ru \
/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®