public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jamie Lokier <jamie@shareable.org>
To: "H. J. Lu" <hjl@lucon.org>
Cc: Arjan van de Ven <arjanv@redhat.com>,
	linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: How to make stack executable on demand?
Date: Mon, 19 Apr 2004 01:08:47 +0100	[thread overview]
Message-ID: <20040419000847.GB11064@mail.shareable.org> (raw)
In-Reply-To: <20040416204651.GA24194@lucon.org>

H. J. Lu wrote:
> On Fri, Apr 16, 2004 at 10:02:58PM +0200, Arjan van de Ven wrote:
> > >  But it will either fail if
> > > kernel is set with non-executable stack,
> > 
> > eh no. mprotect with prot_exec is still supposed to work. The stacks
> > still have MAY_EXEC attribute, just not the actual EXEC attribute
> 
> [...]
> The VM_MAYEXEC bit is untouched. Now the question is if it is a good
> idea for user to change stack permission.

You can create a new executable data area with mmap(), copy the stack
to it, unmap the stack, and mremap() to move the copy to where the
stack was.  The run time linker can do this if you're on a kernel
where mprotect() fails.

In other words, even those kernels which disable VM_MAYEXEC don't
protect against this alternative way of simulating mprotect().  There
is no point in them prohibiting it.

-- Jamie

      parent reply	other threads:[~2004-04-19  0:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-16 17:09 How to make stack executable on demand? H. J. Lu
2004-04-16 18:07 ` Andreas Steinmetz
2004-04-16 19:40   ` H. J. Lu
2004-04-19 14:39   ` Pavel Machek
2004-04-16 20:02 ` Arjan van de Ven
2004-04-16 20:46   ` H. J. Lu
2004-04-16 20:57     ` Dave Jones
2004-04-17  7:13     ` Arjan van de Ven
2004-04-19  0:08     ` Jamie Lokier [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=20040419000847.GB11064@mail.shareable.org \
    --to=jamie@shareable.org \
    --cc=arjanv@redhat.com \
    --cc=hjl@lucon.org \
    --cc=linux-kernel@vger.kernel.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