From: Franck Bui-Huu <vagabon.xyz@gmail.com>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: nigel@mips.com, linux-mips <linux-mips@linux-mips.org>
Subject: Useless stack randomization patch
Date: Wed, 26 Sep 2007 16:10:14 +0200 [thread overview]
Message-ID: <46FA6846.2080704@gmail.com> (raw)
Ralf,
We started stack inside page randomization through commit
941091024ef0f2f7e09eb81201d293ac18833cc8 but it currently does nothing
usefull because ELF_PLATFORM is not defined on MIPS (see
fs/binfm_elf.c, create_elf_tables() for details).
I tried several times to get information on lkml about that dependency
but unfortunately I got no answer.
I'm not sure how ELF_PLATFORM is used by ld.so and I don't think it's
a good idea to define it just for enabling stack randomization.
What do you think ?
thanks
Franck
next reply other threads:[~2007-09-26 14:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-26 14:10 Franck Bui-Huu [this message]
2007-09-26 14:22 ` Useless stack randomization patch Markus Gothe
2007-09-26 14:27 ` Franck Bui-Huu
2007-09-26 15:04 ` Ralf Baechle
2007-09-26 15:20 ` Franck Bui-Huu
2007-09-27 14:57 ` Ralf Baechle
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=46FA6846.2080704@gmail.com \
--to=vagabon.xyz@gmail.com \
--cc=linux-mips@linux-mips.org \
--cc=nigel@mips.com \
--cc=ralf@linux-mips.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