From: Rich Felker <dalias@libc.org>
To: Alexey Izbyshev <izbyshev@ispras.ru>
Cc: musl@lists.openwall.com
Subject: Re: __synccall: deadlock and reliance on racy /proc/self/task
Date: Wed, 20 Feb 2019 19:41:53 -0500 [thread overview]
Message-ID: <20190221004153.GE23599@brightrain.aerifal.cx> (raw)
In-Reply-To: <20190212184849.GO23599@brightrain.aerifal.cx>
On Tue, Feb 12, 2019 at 01:48:49PM -0500, Rich Felker wrote:
> On Sun, Feb 03, 2019 at 12:40:39AM +0300, Alexey Izbyshev wrote:
> > Hello!
> >
> > I've discovered that setuid() deadlocks on a simple stress test
> > (attached: test-setuid.c) that creates threads concurrently with
> > setuid(). (Tested on 1.1.21 on x86_64, kernel 4.15.x and 4.4.x). The
> > gdb output:
>
> FYI I just posted the start of a new thread describing the possible
> thread list design:
>
> https://www.openwall.com/lists/musl/2019/02/12/14
>
> If you want to reply into it the message-id for replies is,
>
> Message-ID: <20190212182625.GA24199@brightrain.aerifal.cx>
>
> (still wish the openwall archive showed those...)
I believe this issue should be entirely fixed now in git master.
When you have time to test, the relevant commits are
e4235d70672d9751d7718ddc2b52d0b426430768 and the few leading up to it.
Rich
prev parent reply other threads:[~2019-02-21 0:41 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-02 21:40 Alexey Izbyshev
2019-02-07 18:36 ` Rich Felker
2019-02-08 18:14 ` Alexey Izbyshev
2019-02-08 18:33 ` Rich Felker
2019-02-09 16:21 ` Szabolcs Nagy
2019-02-09 18:33 ` Alexey Izbyshev
2019-02-09 21:40 ` Szabolcs Nagy
2019-02-09 22:29 ` Alexey Izbyshev
2019-02-10 0:52 ` Rich Felker
2019-02-10 1:16 ` Szabolcs Nagy
2019-02-10 1:20 ` Rich Felker
2019-02-10 4:01 ` Rich Felker
2019-02-10 12:32 ` Szabolcs Nagy
2019-02-10 15:05 ` Rich Felker
2019-02-10 12:15 ` Alexey Izbyshev
2019-02-10 14:57 ` Rich Felker
2019-02-10 21:04 ` Alexey Izbyshev
2019-02-12 18:48 ` Rich Felker
2019-02-21 0:41 ` 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=20190221004153.GE23599@brightrain.aerifal.cx \
--to=dalias@libc.org \
--cc=izbyshev@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).