From: Alexander Monakov <amonakov@ispras.ru>
To: musl@lists.openwall.com
Subject: Re: Use-after-free in __unlock
Date: Thu, 1 Jun 2017 18:42:05 +0300 (MSK) [thread overview]
Message-ID: <alpine.LNX.2.20.13.1706011839280.25404@monopod.intra.ispras.ru> (raw)
In-Reply-To: <CAFnh-mfmsFLbjqJ4ORjq6Ov+dpk2uwJSZzyKiL8yFmmG4biVBw@mail.gmail.com>
This is probably due to logic error (recently mentioned either on this list or
#musl irc) in pthread_create.c, handling of self->startlock between
__pthread_create and (static) start() is inconsistent.
Alexander
next prev parent reply other threads:[~2017-06-01 15:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-01 15:32 Alex Crichton
2017-06-01 15:42 ` Alexander Monakov [this message]
2017-06-01 15:57 ` Rich Felker
2017-06-01 16:16 ` Rich Felker
2017-06-02 5:48 ` Joakim Sindholt
2017-06-02 10:11 ` Jens Gustedt
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=alpine.LNX.2.20.13.1706011839280.25404@monopod.intra.ispras.ru \
--to=amonakov@ispras.ru \
--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).