From: James Courtier-Dutton <James@superbug.co.uk>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Franck Pommereau <pommereau@univ-paris12.fr>,
linux-kernel@vger.kernel.org
Subject: Re: Executability of the stack
Date: Thu, 14 Dec 2006 12:36:20 +0000 [thread overview]
Message-ID: <45814544.1050102@superbug.co.uk> (raw)
In-Reply-To: <1166090244.27217.978.camel@laptopd505.fenrus.org>
Arjan van de Ven wrote:
> On Thu, 2006-12-14 at 10:26 +0100, Franck Pommereau wrote:
>> Dear Linux developers,
>>
>> I recently discovered that the Linux kernel on 32 bits x86 processors
>> reports the stack as being non-executable while it is actually
>> executable (because located in the same memory segment).
>
> this is not per se true, it depends on the capabilities of your 32 bit
> x86 processor.
>
>
>> # grep maps /proc/self/maps
>> bfce8000-bfcfe000 rw-p bfce8000 00:00 0 [stack]
>
> this shows that the *intent* is to have it non-executable.
> Not all x86 processors can enforce this. All modern ones do.
>
>> Is there any reason for this situation?
>
> the alternative (showing effective permission) is equally confusing;
> apps would see permissions they didn't set...
>
Why not show both.
"intent" and "effective".
next prev parent reply other threads:[~2006-12-14 12:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-14 9:26 Executability of the stack Franck Pommereau
2006-12-14 9:57 ` Arjan van de Ven
2006-12-14 12:07 ` Franck Pommereau
2006-12-14 12:19 ` Arjan van de Ven
2006-12-14 15:17 ` [PATCH] Clarify i386/Kconfig explanation of the HIGHMEM config options Theodore Tso
2006-12-14 15:27 ` thunder7
2006-12-14 15:37 ` Theodore Tso
2006-12-14 16:06 ` Arjan van de Ven
2006-12-14 16:11 ` Avi Kivity
2006-12-14 19:58 ` Alistair John Strachan
2006-12-15 17:06 ` Bill Davidsen
2006-12-14 15:52 ` Arjan van de Ven
2006-12-14 12:36 ` James Courtier-Dutton [this message]
[not found] ` <1166099950.27217.1024.camel@laptopd505.fenrus.org>
2006-12-14 14:55 ` Executability of the stack Franck Pommereau
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=45814544.1050102@superbug.co.uk \
--to=james@superbug.co.uk \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pommereau@univ-paris12.fr \
/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