From: Ralf Baechle <ralf@linux-mips.org>
To: Franck Bui-Huu <vagabon.xyz@gmail.com>
Cc: nigel@mips.com, linux-mips <linux-mips@linux-mips.org>
Subject: Re: Useless stack randomization patch
Date: Thu, 27 Sep 2007 15:57:12 +0100 [thread overview]
Message-ID: <20070927145712.GA10377@linux-mips.org> (raw)
In-Reply-To: <46FA78AA.9050104@gmail.com>
On Wed, Sep 26, 2007 at 05:20:10PM +0200, Franck Bui-Huu wrote:
> Ralf Baechle wrote:
> > On Wed, Sep 26, 2007 at 04:10:14PM +0200, Franck Bui-Huu wrote:
> > I suppose we should give it a sane definition. Not sure what would be
> > useful, if it should be like an ASCII string with the processor type or
> > more corse grained like just "mips32r2", should ASEs be mentioned ...
> >
>
> Well before giving any sane definition, shouldn't we know why this
> dependency (ELF_PLATFORM/sp-randomization) exists at all...
>
> Is something like the patch below better ?
Yes, I think that makes more sense.
Ralf
prev parent reply other threads:[~2007-09-27 14:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-26 14:10 Useless stack randomization patch Franck Bui-Huu
2007-09-26 14:22 ` 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 [this message]
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=20070927145712.GA10377@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=linux-mips@linux-mips.org \
--cc=nigel@mips.com \
--cc=vagabon.xyz@gmail.com \
/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