public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. J. Lu" <hjl@lucon.org>
To: Arjan van de Ven <arjanv@redhat.com>
Cc: linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: How to make stack executable on demand?
Date: Fri, 16 Apr 2004 13:46:51 -0700	[thread overview]
Message-ID: <20040416204651.GA24194@lucon.org> (raw)
In-Reply-To: <1082145778.9600.6.camel@laptop.fenrus.com>

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

Ok. It looks like a bug in Red Hat EL 3 kernel. In fs/exec.c, there
are

                if (executable_stack)
                        mpnt->vm_flags = VM_STACK_FLAGS | VM_MAYEXEC | VM_EXEC;
		else
                        mpnt->vm_flags = VM_STACK_FLAGS & ~(VM_MAYEXEC|VM_EXEC); 

That is if an executabl is not marked with executable stack, the
VM_MAYEXEC bit is turned off. But 2.6.5-mm6 has

                if (unlikely(executable_stack == EXSTACK_ENABLE_X))
                        mpnt->vm_flags = VM_STACK_FLAGS |  VM_EXEC;
                else if (executable_stack == EXSTACK_DISABLE_X)
                        mpnt->vm_flags = VM_STACK_FLAGS & ~VM_EXEC;
                else
                        mpnt->vm_flags = VM_STACK_FLAGS;
  
The VM_MAYEXEC bit is untouched. Now the question is if it is a good
idea for user to change stack permission.


H.J.

  reply	other threads:[~2004-04-16 20:48 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 [this message]
2004-04-16 20:57     ` Dave Jones
2004-04-17  7:13     ` Arjan van de Ven
2004-04-19  0:08     ` Jamie Lokier

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=20040416204651.GA24194@lucon.org \
    --to=hjl@lucon.org \
    --cc=arjanv@redhat.com \
    --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