[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <300a1bdb9e9041bf05312ef032cbdc66@yqxmail.com>
Date: Tue, 30 Jun 2020 14:00:13 -0700
From: Hydro Flask <hydroflask@...mail.com>
To: musl@...ts.openwall.com
Cc: Rich Felker <dalias@...c.org>
Subject: Re: Potential deadlock in pthread_kill()
On 2020-06-30 12:54, Rich Felker wrote:
> Note that for fixing this issue, it won't suffice just to make
> pthread_kill block signals. The other places that use the killlock
> also need to block signals, to make the lock fully AS-safe.
>
> Rich
Rich did you see the issue I was talking about in the example in my
previous email? Does it make sense?
I do not mind submitting a patch for this issue if you don't currently
have the spare cycles, just let me know if we are in agreement in terms
of understanding the issue and I can submit a patch that blocks "app
signals" in every place that uses the killlock.
Probably could also remove the pthread_self() special case that you
referenced earlier in the thread but that would be a second patch.
Thank you,
Hydro
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.
