mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Szabolcs Nagy <nsz@port70.net>
To: musl@lists.openwall.com
Cc: LeMay@port70.net, Michael <michael.lemay@intel.com>
Subject: Re: [RFC] Support for segmentation-hardened SafeStack
Date: Fri, 23 Sep 2016 12:22:02 +0200	[thread overview]
Message-ID: <20160923102202.GB1280@port70.net> (raw)
In-Reply-To: <390CE752059EB848A71F4F676EBAB76D3AC0B184@ORSMSX114.amr.corp.intel.com>

* LeMay, Michael <michael.lemay@intel.com> [2016-09-22 23:00:45 +0000]:
> I submitted several patches to LLVM and Clang to harden SafeStack using segmentation on x86-32 [1].  See [2] for general background on SafeStack.
...
> [1] http://lists.llvm.org/pipermail/llvm-dev/2016-May/100346.html
> [2] http://clang.llvm.org/docs/SafeStack.html

is all runtime support in the libc with your patches?
(i.e. no static linked interposition code from compiler-rt)

can you call into non-instrumented code?
(as Rich noted this looks like a new abi on i386)
i assume the segmented variant breaks abi while the
non-segmented one does not.

what is the unsafe stack size of the main thread?
how much is the resource usage overhead?

what happens if unsafe stack allocation fails?
how does the stack get deallocated at thread exit?
i assume they are consistent with normal stack
handling if this is done in musl.. except for the
main thread.

can signal handlers work with sigaltstack?


  parent reply	other threads:[~2016-09-23 10:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-22 23:00 LeMay, Michael
2016-09-22 23:42 ` Rich Felker
2016-09-26 17:28   ` LeMay, Michael
2016-09-26 18:08     ` Rich Felker
2016-09-27  6:05       ` LeMay, Michael
2016-09-27 14:43         ` Rich Felker
2016-09-27 21:35           ` LeMay, Michael
2016-09-23 10:22 ` Szabolcs Nagy [this message]
2016-09-26 17:55   ` LeMay, Michael

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=20160923102202.GB1280@port70.net \
    --to=nsz@port70.net \
    --cc=LeMay@port70.net \
    --cc=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).