From: Szabolcs Nagy <nsz@port70.net>
To: musl@lists.openwall.com
Subject: glibc dynamic thread local storage issues
Date: Mon, 28 Nov 2016 20:17:49 +0100 [thread overview]
Message-ID: <20161128191749.GA5749@port70.net> (raw)
in case somebody needs an argument why the musl dynamic linker
is safer, i listed some of the glibc tls handling issues
(see Current design bugs section):
https://sourceware.org/ml/libc-alpha/2016-11/msg01026.html
(this is far from covering all dynamic linker bugs in glibc, only
code paths related to a particular pthread_create vs dlopen data
race were analyzed that i was trying to fix before.)
reply other threads:[~2016-11-28 19:17 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=20161128191749.GA5749@port70.net \
--to=nsz@port70.net \
--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).