Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Thiemo Seufer <ths@networkno.de>
To: "Kevin D. Kissell" <KevinK@paralogos.com>
Cc: Brian Foster <brian.foster@innova-card.com>,
	linux-mips@linux-mips.org, Andrew Dyer <adyer@righthandtech.com>
Subject: Re: Adding(?) XI support to MIPS-Linux?
Date: Mon, 9 Jun 2008 21:46:27 +0100	[thread overview]
Message-ID: <20080609204627.GE11233@networkno.de> (raw)
In-Reply-To: <484D856B.5030306@paralogos.com>

Kevin D. Kissell wrote:
[snip]
>>  Broadly, what I'm trying to say is I don't want to touch gcc
>>  (and/or binutils) and am unconvinced I have to.  But I'm very
>>  much open to correction here!
>>
>>  The x86 (including amd64) and, AFAIK, SuperH (sh) Linux kernels
>>  now support NX or equivalent; indeed, a test on my 2.6.22(-ish)
>>  amd64 workstation (Kubuntu 7.10) has a non-executable stack.
>>  As such, those could be a model worth studying/following, but
>>  I understand they have support for specially-marked binaries to
>>  have executable stacks (i.e., binutils/gcc mods, which I want to
>>  avoid).
> Well, strictly speaking, you wouldn't actually *need* to modify binutils
> to make specially tagged binaries.  You could borrow an unused bit in
> the ELF header somewhere, have the kernel recognize it, and write your
> own little tool that only turns that bit on/off in an ELF file.

This exists already in ld's -z execstack/noexecstack feature. It is
not used by default because too many things depend on executable
stacks on MIPS.


Thiemo

  reply	other threads:[~2008-06-09 20:46 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 [this message]
     [not found]       ` <200806101119.06227.brian.foster@innova-card.com>
2008-06-10  9:32         ` Brian Foster
2008-06-10  9:57           ` Thiemo Seufer
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=20080609204627.GE11233@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