From: Florian Weimer <fweimer@redhat.com>
To: Nix <nix@esperi.org.uk>, libc-alpha@sourceware.org
Subject: Re: [PATCH 09/15] De-PLTize __stack_chk_fail internal calls within libc.so.
Date: Wed, 21 Dec 2016 15:05:00 -0000 [thread overview]
Message-ID: <5ea34e08-3e6b-4e5c-6044-5cb7831316ea@redhat.com> (raw)
In-Reply-To: <20161219111528.14969-10-nix@esperi.org.uk>
On 12/19/2016 12:15 PM, Nix wrote:
> From: Adhemerval Zanella <adhemerval.zanella@linaro.org>
>
> We use the same assembler-macro trick we use to de-PLTize
> compiler-generated libcalls to memcpy and memset to redirect
> __stack_chk_fail to __stack_chk_fail_local.
>
> v5: New.
> v6: Only do it within the shared library: with __stack_chk_fail_local
> in libc_pic.a now we don't need to worry about calls from inside
> other routines in libc_nonshared.a any more.
> v8: Merge #ifdef blocks.
> v10: Use STACK_PROTECTOR_LEVEL to avoid renaming in files where
> stack-protection is suppressed.
>
> * sysdeps/generic/symbol-hacks.h [STACK_PROTECTOR_LEVEL &&
> STACK_PROTECTOR_LEVEL > 0] (__stack_chk_fail): Add internal alias.
I'm going to fold this into the previous commit.
Thanks,
Florian
next prev parent reply other threads:[~2016-12-21 15:05 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-19 11:15 --enable-stack-protector for glibc, v10 Nix
2016-12-19 11:15 ` [PATCH 06/15] Prevent the rtld mapfile computation from dragging in __stack_chk_fail* Nix
2016-12-19 11:15 ` [PATCH 04/15] Mark all machinery needed in early static-link init as -fno-stack-protector Nix
2016-12-21 14:18 ` Florian Weimer
2016-12-19 11:15 ` [PATCH 08/15] Add a hidden __stack_chk_fail_local alias to libc.so Nix
2016-12-19 11:25 ` [PATCH 09/15] De-PLTize __stack_chk_fail internal calls within libc.so Nix
2016-12-21 15:05 ` Florian Weimer [this message]
2016-12-22 22:41 ` Nix
2016-12-19 11:25 ` [PATCH 14/15] tst-quad1pie, tst-quad2pie: compile with -fPIE Nix
2016-12-21 13:36 ` Florian Weimer
2016-12-19 11:25 ` [PATCH 11/15] Drop explicit stack-protection of pieces of the system Nix
2016-12-19 11:25 ` [PATCH 10/15] Link a non-libc-using test with -fno-stack-protector Nix
2016-12-19 11:25 ` [PATCH 15/15] Enable -fstack-protector=* when requested by configure Nix
2016-12-19 11:26 ` [PATCH 01/15] Configury support for --enable-stack-protector Nix
2016-12-19 11:26 ` [PATCH 13/15] Move all tests out of csu Nix
2016-12-21 13:36 ` Florian Weimer
2016-12-19 11:26 ` [PATCH 12/15] Do not stack-protect sigreturn stubs Nix
2016-12-19 11:26 ` [PATCH 02/15] Initialize the stack guard earlier when linking statically Nix
2016-12-21 14:16 ` Florian Weimer
2016-12-21 20:15 ` Florian Weimer
2016-12-22 22:38 ` Nix
2016-12-19 11:26 ` [PATCH 05/15] Compile the entire dynamic linker with -fno-stack-protector Nix
2016-12-21 14:18 ` Florian Weimer
2016-12-21 14:25 ` Szabolcs Nagy
2016-12-21 14:57 ` Florian Weimer
2016-12-19 11:27 ` [PATCH 07/15] Work even with compilers hacked to enable -fstack-protector by default Nix
2016-12-19 11:27 ` [PATCH 03/15] Do not stack-protect ifunc resolvers Nix
2016-12-21 14:17 ` Florian Weimer
2016-12-22 22:40 ` Nix
2016-12-19 15:15 ` --enable-stack-protector for glibc, v10 Florian Weimer
2016-12-19 15:18 ` Chris Metcalf
2016-12-19 15:54 ` Nix
2016-12-20 8:30 ` Florian Weimer
2016-12-20 19:04 ` Nix
2016-12-21 17:26 ` Florian Weimer
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=5ea34e08-3e6b-4e5c-6044-5cb7831316ea@redhat.com \
--to=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=nix@esperi.org.uk \
/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).