From: Samuel Thibault <samuel.thibault@ens-lyon.org>
To: Nick Alcock <nix@esperi.org.uk>
Cc: libc-alpha@sourceware.org
Subject: Re: [hurd,commited]: Fix static initialization with -fstack-protector-strong
Date: Fri, 15 Sep 2017 21:22:00 -0000 [thread overview]
Message-ID: <20170915212231.acizqralo6yggv4a@var.youpi.perso.aquilenet.fr> (raw)
In-Reply-To: <871sn7q5m9.fsf@esperi.org.uk>
Nick Alcock, on ven. 15 sept. 2017 17:38:38 +0100, wrote:
> On 27 Aug 2017, Samuel Thibault outgrape:
> > When linked statically, TLS initialization is not achieved before
> > mach_init and alike, so ssp accesses to tcbhead's stack_guard would
> > crash. We can just avoid using ssp in the few functions needed before
> > TLS is set up.
>
> Oh blast I forgot all about Hurd didn't I.
>
> Sorry.
No problem. Determining which functions need it is not trivial anyway :)
Samuel
prev parent reply other threads:[~2017-09-15 21:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-27 20:32 Samuel Thibault
2017-09-15 16:38 ` Nick Alcock
2017-09-15 21:22 ` Samuel Thibault [this message]
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=20170915212231.acizqralo6yggv4a@var.youpi.perso.aquilenet.fr \
--to=samuel.thibault@ens-lyon.org \
--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).