mailing list of musl libc
 help / color / mirror / code / Atom feed
From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: pthread_key_create bug?
Date: Sun, 6 Jan 2019 21:11:28 -0500	[thread overview]
Message-ID: <20190107021128.GW23599@brightrain.aerifal.cx> (raw)
In-Reply-To: <5c1d9cf6-1b53-7082-5dee-8673ed4c55e9@adelielinux.org>

On Sun, Jan 06, 2019 at 08:50:46AM -0600, A. Wilcox wrote:
> On 01/06/19 08:35, Nathaniel Pierce wrote:
> > Hello -
> > 
> > I believe I’ve encountered a bug in musl’s pthread_key_create().
> > Immediately after key creation, pthread_getspecific() may not return
> > NULL. Here’s a gist with details and a test that fails:
> > 
> > https://gist.github.com/nwpierce/df17c17571431a30c16999b6d0dd123f
> > 
> > I’m running musl-1.1.19-r10 as part of Alpine 3.8.1 (via Docker).
> > 
> > Thanks!
> > 
> > -Nate
> 
> 
> We identified this bug in August 2018:
> 
> https://wiki.adelielinux.org/wiki/POSIX#pthread_getspecific
> 
> I had thought there had been progress, but I can't find any ML messages
> mentioning it, and your test case asserts during pass 2 on musl 1.1.20
> on my workstation running Adélie beta2/ppc64.

See commit 84d061d5a31c9c773e29e1e2b1ffe8cb9557bc58.

Rich


  parent reply	other threads:[~2019-01-07  2:11 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-06 14:35 Nathaniel Pierce
2019-01-06 14:50 ` A. Wilcox
2019-01-06 16:28   ` Szabolcs Nagy
2019-01-07  2:11   ` Rich Felker [this message]
2019-01-07 12:24     ` A. Wilcox
2019-01-07 14:12       ` Rich Felker
2019-01-07 17:13     ` Markus Wichmann
2019-01-08  0:00       ` Rich Felker
2019-01-08  8:43         ` u-uy74
2019-01-08 19:34           ` Markus Wichmann
2019-01-08 22:40             ` writeonce
2019-01-08 22:10         ` Markus Wichmann
2019-01-08 23:07           ` A. Wilcox
2019-01-09  0:29           ` Rich Felker
2019-01-09 11:45             ` Szabolcs Nagy

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=20190107021128.GW23599@brightrain.aerifal.cx \
    --to=dalias@libc.org \
    --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).