From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: Draft outline of thread-list design
Date: Thu, 14 Feb 2019 19:20:02 -0500 [thread overview]
Message-ID: <20190215002002.GZ23599@brightrain.aerifal.cx> (raw)
In-Reply-To: <20190212182625.GA24199@brightrain.aerifal.cx>
On Tue, Feb 12, 2019 at 01:26:25PM -0500, Rich Felker wrote:
> Here's a draft of the thread-list design, proposed previously as a
> better way to do dynamic TLS installation, and now as a solution to
> the problem of __synccall's use of /proc/self/task being (apparently
> hopelessly) broken:
>
>
>
> Goal of simplicity and correctness, not micro-optimizing.
>
> List lock is fully AS-safe. Taking lock requires signals be blocked.
To elaborate on this: application signals must be blocked before the
lock is taken, but implementation signals (particularly the synccall
signal) must not be blocked. Otherwise there is a deadlock: it's
possible that thread A is waiting for the thread list lock, and thread
B holds the thread list lock and is waiting for thread A to respond to
a synccall signal before it can make forward progress.
If we want to block *all* signals, which is needed at detached thread
exit to prevent delivery in the absence of a stack, they must be
blocked after obtaining the thread list lock.
Rich
prev parent reply other threads:[~2019-02-15 0:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-12 18:26 Rich Felker
2019-02-12 20:23 ` Rich Felker
2019-02-14 21:16 ` Alexey Izbyshev
2019-02-14 22:32 ` Rich Felker
2019-02-14 22:54 ` Alexey Izbyshev
2019-02-14 23:19 ` Rich Felker
2019-02-15 0:20 ` Rich Felker [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=20190215002002.GZ23599@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).