From: Andrew Morton <akpm@linux-foundation.org>
To: Jan Kratochvil <honza@jikos.cz>
Cc: Ingo Molnar <mingo@elte.hu>, Jiri Kosina <jikos@jikos.cz>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH][RESEND] PIE randomization
Date: Fri, 11 May 2007 12:56:29 -0700 [thread overview]
Message-ID: <20070511125629.3df919cf.akpm@linux-foundation.org> (raw)
In-Reply-To: <alpine.LRH.0.98.0705111338230.22353@twin.jikos.cz>
On Fri, 11 May 2007 14:33:46 +0200 (CEST)
Jan Kratochvil <honza@jikos.cz> wrote:
> Hello,
> I sent this patch 5 days ago, nobody replied. So I am giving it second
> attempt.
> Andrew, is it possible to test this in -mm branch?
> Original mail follows:
>
> Hi,
> this is something like reaction to this thread:
> http://lkml.org/lkml/2007/1/6/124. I hope I was able to separate the PIE
> randomization part correctly.
>
> There is platform specific (__i386__ only) part in exec shield, I am not
> pretty sure why is it there, but wasn't brave enough to touch it. Can
> someone comment the #ifdef out and test it on some other platform?
>
> It will be nice to follow with brk randomization, but in exec-shield it is
> afaik i386 only. Right?
>
> Randomizes -pie compiled binaries. The implementation is part of Redhat's
> exec-shield (http://people.redhat.com/mingo/exec-shield/).
>
I don't know what to do with this. The changelog doesn't tell me what PIE
randomization _is_, nor why the kernel would want to do it.
"Randomizing -pie compiled binaries" sounds fairly undesirable, actually ;)
>
> diff --git a/fs/binfmt_elf.c b/fs/binfmt_elf.c
> index 9cc4f0a..1156f41 100644
> --- a/fs/binfmt_elf.c
> +++ b/fs/binfmt_elf.c
> @@ -45,7 +45,7 @@
>
> static int load_elf_binary(struct linux_binprm *bprm, struct pt_regs *regs);
> static int load_elf_library(struct file *);
> -static unsigned long elf_map (struct file *, unsigned long, struct elf_phdr *, int, int);
> +static unsigned long elf_map (struct file *, unsigned long, struct elf_phdr *, int, int, unsigned long);
Your email client is space-stuffing the patches. That's easy to fix at the
receiving end, but it'd be better to fix it at the sending end, please.
next prev parent reply other threads:[~2007-05-11 19:57 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-11 12:33 [PATCH][RESEND] PIE randomization Jan Kratochvil
2007-05-11 19:56 ` Andrew Morton [this message]
2007-05-11 20:18 ` Jiri Kosina
2007-05-11 20:36 ` Andrew Morton
2007-05-11 22:41 ` Ulrich Drepper
2007-05-11 23:50 ` Jiri Kosina
2007-05-16 17:14 ` Jiri Kosina
2007-05-17 20:24 ` Jan Kratochvil
2007-05-17 21:50 ` Jiri Kosina
2007-05-18 17:29 ` Andrew Morton
2007-05-21 14:58 ` Hugh Dickins
2007-05-22 23:16 ` Andrew Morton
2007-05-23 8:50 ` Jiri Kosina
2007-07-04 8:25 ` Jakub Jelinek
2007-07-04 17:35 ` Jiri Kosina
2007-07-05 20:53 ` Chuck Ebbert
2007-07-05 20:57 ` Rik van Riel
2007-07-07 0:13 ` Jiri Kosina
2007-07-07 12:30 ` Jakub Jelinek
2007-07-09 11:41 ` Jiri Kosina
2007-07-09 21:58 ` Jiri Kosina
2007-07-10 9:47 ` Jakub Jelinek
2007-07-11 9:58 ` 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=20070511125629.3df919cf.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=honza@jikos.cz \
--cc=jikos@jikos.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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