From: "LeMay, Michael" <michael.lemay@intel.com>
To: "musl@lists.openwall.com" <musl@lists.openwall.com>
Subject: [RFC PATCH 0/7] Segmentation-hardened SafeStack support
Date: Tue, 27 Sep 2016 15:33:03 -0700 [thread overview]
Message-ID: <2440e731-89e5-e674-9390-0de98533e744@intel.com> (raw)
Here is the current revision of my patches for providing
segmentation-hardened SafeStack support.
See http://lists.llvm.org/pipermail/llvm-dev/2016-May/100346.html for
information on the corresponding compiler patches.
Comments appreciated.
Michael LeMay (7):
add --enable-safe-stack configuration option
avoid invoking the vDSO when SafeStack is enabled
disable check for buggy brk implementations when SafeStack is enabled
add stack segment override prefix to i386 __clone
support SafeStack in init and threading
support dynamic linking with segmentation-hardened SafeStack
add compiler flags to enable SafeStack
Makefile | 8 ++
arch/i386/syscall_arch.h | 13 +++
configure | 5 +
ldso/dlstart.c | 23 ++++-
ldso/dynlink.c | 44 ++++++--
src/env/__libc_start_main.c | 19 ++++
src/env/__safestack.c | 241
++++++++++++++++++++++++++++++++++++++++++++
src/internal/pthread_impl.h | 4 +
src/malloc/expand_heap.c | 2 +
src/thread/i386/clone.s | 2 +-
src/thread/pthread_create.c | 72 ++++++++++++-
11 files changed, 420 insertions(+), 13 deletions(-)
create mode 100644 src/env/__safestack.c
--
2.7.4
reply other threads:[~2016-09-27 22:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=2440e731-89e5-e674-9390-0de98533e744@intel.com \
--to=michael.lemay@intel.com \
--cc=musl@lists.openwall.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).