From: "H. J. Lu" <hjl@lucon.org>
To: linux kernel <linux-kernel@vger.kernel.org>
Subject: How to make stack executable on demand?
Date: Fri, 16 Apr 2004 10:09:15 -0700 [thread overview]
Message-ID: <20040416170915.GA20260@lucon.org> (raw)
With the non-executable stack kernel, how can I make stack executable
on demand? If I set kernel with non-executable stack, only those
binaries marked with executable PT_GNU_STACK will have executable
stack. But a binary with non-executable PT_GNU_STACK may dlopen a
DSO with executable PT_GNU_STACK. The dynamic linker will try to
make stack executable with mprotect. But it will either fail if
kernel is set with non-executable stack, or be a no-op if kernel
is set with executable stack. Is there a third option that a process
starts with non-executable stack and can change the stack permission
later?
H.J.
next reply other threads:[~2004-04-16 17:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-16 17:09 H. J. Lu [this message]
2004-04-16 18:07 ` How to make stack executable on demand? 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
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=20040416170915.GA20260@lucon.org \
--to=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