From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.org/gmane.linux.lib.musl.general/10754 Path: news.gmane.org!.POSTED!not-for-mail From: Szabolcs Nagy Newsgroups: gmane.linux.lib.musl.general Subject: glibc dynamic thread local storage issues Date: Mon, 28 Nov 2016 20:17:49 +0100 Message-ID: <20161128191749.GA5749@port70.net> Reply-To: musl@lists.openwall.com NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: blaine.gmane.org 1480360688 19538 195.159.176.226 (28 Nov 2016 19:18:08 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Mon, 28 Nov 2016 19:18:08 +0000 (UTC) User-Agent: Mutt/1.6.0 (2016-04-01) To: musl@lists.openwall.com Original-X-From: musl-return-10767-gllmg-musl=m.gmane.org@lists.openwall.com Mon Nov 28 20:18:02 2016 Return-path: Envelope-to: gllmg-musl@m.gmane.org Original-Received: from mother.openwall.net ([195.42.179.200]) by blaine.gmane.org with smtp (Exim 4.84_2) (envelope-from ) id 1cBRRB-00046S-Ks for gllmg-musl@m.gmane.org; Mon, 28 Nov 2016 20:18:01 +0100 Original-Received: (qmail 24109 invoked by uid 550); 28 Nov 2016 19:18:03 -0000 Mailing-List: contact musl-help@lists.openwall.com; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-ID: Original-Received: (qmail 24071 invoked from network); 28 Nov 2016 19:18:01 -0000 Mail-Followup-To: musl@lists.openwall.com Content-Disposition: inline Xref: news.gmane.org gmane.linux.lib.musl.general:10754 Archived-At: 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.)