[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20190221004153.GE23599@brightrain.aerifal.cx>
Date: Wed, 20 Feb 2019 19:41:53 -0500
From: Rich Felker <dalias@...c.org>
To: Alexey Izbyshev <izbyshev@...ras.ru>
Cc: musl@...ts.openwall.com
Subject: Re: __synccall: deadlock and reliance on racy /proc/self/task
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@...ghtrain.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
Powered by blists - more mailing lists
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
