From: Thiemo Seufer <ths@networkno.de>
To: Brian Foster <brian.foster@innova-card.com>
Cc: "Kevin D. Kissell" <KevinK@paralogos.com>,
Andrew Dyer <adyer@righthandtech.com>,
linux-mips@linux-mips.org
Subject: Re: Adding(?) XI support to MIPS-Linux?
Date: Tue, 10 Jun 2008 10:57:02 +0100 [thread overview]
Message-ID: <20080610095702.GG11233@networkno.de> (raw)
In-Reply-To: <a537dd660806100232v4cbf2cfeo397e94ac5a4d2104@mail.gmail.com>
Brian Foster wrote:
[snip]
> 2) Kevin D. Kissell wrote:
> 2)[ ... ]
> 2) > Well, strictly speaking, you wouldn't actually *need* to modify
> 2) > binutils to make specially tagged binaries. [ ... ]
> 2)
> 2) This exists already in ld's -z execstack/noexecstack feature.
>
> Good point. Thanks for the reminder.
>
> 2) It is not used by default because too many things depend on executable
> 2) stacks on MIPS.
>
> Ah! Can you be more specific please? At the present time
> I'm only aware of three situations where executable stacks
> are magically used ("magic" meaning it's being done without
> the programmer explicitly coding it):
>
> 1. sigreturn.
> 2. something to do with FPU emulation?
> 3. pointer to a nested function (gcc extension).
Those, plus manually coded trampolines in e.g. foreign function
interfacing (which are typically hidden in some library). I don't
know if you can ignore that completely. :-)
> And, significantly, I am do not know of any need for the
> kernel-mode stacks to be executable. Except, perhaps,
> for case 3, the above are (should be?) user-land only.
AFAIK nested functions are frowned upon in kernelspace.
Thiemo
next prev parent reply other threads:[~2008-06-10 9:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200806091658.10937.brian.foster@innova-card.com>
2008-06-09 15:37 ` Re: Adding(?) XI support to MIPS-Linux? Brian Foster
2008-06-09 19:32 ` Kevin D. Kissell
2008-06-09 20:46 ` Thiemo Seufer
[not found] ` <200806101119.06227.brian.foster@innova-card.com>
2008-06-10 9:32 ` Brian Foster
2008-06-10 9:57 ` Thiemo Seufer [this message]
2008-06-10 16:21 ` David Daney
2008-06-11 13:16 ` Brian Foster
2008-06-11 18:51 ` Kevin D. Kissell
2008-06-12 12:03 ` Brian Foster
2008-06-18 8:42 ` Brian Foster
2008-06-18 9:36 ` Kevin D. Kissell
2008-06-18 9:45 ` Brian Foster
2008-06-11 9:06 ` Ralf Baechle
2008-06-11 9:35 ` Kevin D. Kissell
[not found] <200806091050.m59AoUUl014012@smtp02.msg.oleane.net>
2008-06-09 10:55 ` Brian Foster
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=20080610095702.GG11233@networkno.de \
--to=ths@networkno.de \
--cc=KevinK@paralogos.com \
--cc=adyer@righthandtech.com \
--cc=brian.foster@innova-card.com \
--cc=linux-mips@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