From: Franck Bui-Huu <vagabon.xyz@gmail.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-arch@vger.kernel.org
Subject: ELF randomization questions
Date: Sat, 15 Sep 2007 10:46:15 +0200 [thread overview]
Message-ID: <46EB9BD7.9050209@gmail.com> (raw)
Hello,
I have a couple questions about the process stack randomization but
I'm not sure who should be CCed for such questions.
I submitted a patch to enable 'inside the page' stack randomization on
MIPS few weeks ago and which has been now committed. But I noticed
that this patch is actually useless because this randomization depends
on ELF_PLATFORM symbol to be defined which it isn't on MIPS. All of
this happens in create_elf_tables() function defined in
fs/binfmt_elf.c.
So my first question is now, why is this dependency for ? Can we
remove it and unconditionally do the 'inside the page' randomization
for platforms that implement it ? I'm not sure how ELF_PLATFORM is
used, I guess it is used later by ld.so on certain architectures but
dunno how.
The second question is that the stack randomization is currently
mainly part of the elf code, but shouldn't it be put in exec.c and
thus be used by all others binary handlers ?
thanks for any hints.
Franck
reply other threads:[~2007-09-15 8:47 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=46EB9BD7.9050209@gmail.com \
--to=vagabon.xyz@gmail.com \
--cc=linux-arch@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).