From: Joseph Myers <joseph@codesourcery.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: GNU C Library <libc-alpha@sourceware.org>,
Igor Tsimbalist <igor.v.tsimbalist@intel.com>
Subject: Re: [PATCH] Linux/x86: Support shadow stack pointer in setjmp/longjmp
Date: Mon, 18 Dec 2017 17:44:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.20.1712181741480.26421@digraph.polyomino.org.uk> (raw)
In-Reply-To: <20171218162753.GA25026@gmail.com>
On Mon, 18 Dec 2017, H.J. Lu wrote:
> * sysdeps/unix/sysv/linux/i386/__longjmp.S: New file.
> * sysdeps/unix/sysv/linux/i386/bsd-_setjmp.S: Likewise.
> * sysdeps/unix/sysv/linux/i386/bsd-setjmp.S: Likewise.
> * sysdeps/unix/sysv/linux/i386/setjmp.S: Likewise.
> * sysdeps/unix/sysv/linux/x86_64/__longjmp.S: Likewise.
> * sysdeps/unix/sysv/linux/x86_64/setjmp.S: Likewise.
Why are all these files Linux-specific? ____longjmp_chk is Linux-specific
because it does a sysaltstack syscall, but I don't see anything
OS-specific in these files. Why shouldn't shadow stack support be
available for all OSes on these architectures?
Is support for the relevant instructions available in all binutils
versions supported for building glibc? If not, does __SHSTK__ being
defined guarantee that GCC was built with a binutils version with the
required support, or do we need additional configure checks for binutils
support?
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2017-12-18 17:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-18 16:27 H.J. Lu
2017-12-18 17:44 ` Joseph Myers [this message]
[not found] ` <CAMe9rOr3gEyaJZ7ukNTY=MiSdWnPbmLOqduodyk3Mx8Qn9J58w@mail.gmail.com>
2017-12-18 18:09 ` H.J. Lu
2017-12-18 18:25 ` Joseph Myers
2017-12-18 20:22 ` H.J. Lu
2017-12-19 16:41 ` H.J. Lu
2017-12-19 18:20 ` Zack Weinberg
2017-12-19 18:26 ` H.J. Lu
2017-12-19 18:33 ` Joseph Myers
2017-12-19 18:36 ` H.J. Lu
2017-12-19 18:26 ` Joseph Myers
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=alpine.DEB.2.20.1712181741480.26421@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=hjl.tools@gmail.com \
--cc=igor.v.tsimbalist@intel.com \
--cc=libc-alpha@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).