From: "Milan P. Stanić" <mps@arvanta.net>
To: musl@lists.openwall.com
Subject: Re: [musl] [PATCH v2] MT fork
Date: Thu, 29 Oct 2020 00:06:10 +0100 [thread overview]
Message-ID: <20201028230610.GA3269@arya.arvanta.net> (raw)
In-Reply-To: <20201028185608.GG534@brightrain.aerifal.cx>
On Wed, 2020-10-28 at 14:56, Rich Felker wrote:
> On Tue, Oct 27, 2020 at 05:17:35PM -0400, Rich Felker wrote:
> > > >
> > > > Will follow up with draft patch for testing.
> > >
> > > Patch attached. It should suffice for testing and review of whether
> > > there are any locks/state I overlooked. It could possibly be made less
> > > ugly too.
> > > [...]
> >
> > Another bug:
> > [...]
>
> And an updated version of the patch with both previously reported bugs
> fixed, for the purpose of users/distros wanting to test without
> manually fixing up the patch. Attached.
Applied this patch on top of current musl master, build it on Alpine and
installed.
Tested by building ruby lang. Works fine.
Also tested building zig lang, works fine.
But crystal lang builds fine, but running it hangs. strace shows:
-------------
[pid 5573] futex(0x7efc50fba9e4, FUTEX_WAIT_PRIVATE, 2, NULL <unfinished ...>
[pid 5568] futex(0x7efc5118f984, FUTEX_REQUEUE_PRIVATE, 0, 1, 0x7efc514b67a4) = 1
[pid 5568] futex(0x7efc514b67a4, FUTEX_WAKE_PRIVATE, 1) = 1
[pid 5571] <... futex resumed>) = 0
[pid 5568] futex(0x7efc511099e4, FUTEX_WAIT_PRIVATE, 2, NULL <unfinished ...>
[pid 5571] futex(0x7efc510409e4, FUTEX_WAIT_PRIVATE, 2, NULL
-------------
where it hangs.
--
Regards
[...]
next prev parent reply other threads:[~2020-10-28 23:06 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-26 0:50 [musl] Status report and " Rich Felker
2020-10-26 0:59 ` Rich Felker
2020-10-26 3:29 ` Rich Felker
2020-10-26 18:44 ` Érico Nogueira
2020-10-26 19:52 ` Rich Felker
2020-10-26 20:11 ` Érico Nogueira
2020-10-27 21:17 ` Rich Felker
2020-10-28 18:56 ` [musl] [PATCH v2] " Rich Felker
2020-10-28 23:06 ` Milan P. Stanić [this message]
2020-10-29 16:13 ` Szabolcs Nagy
2020-10-29 16:20 ` Rich Felker
2020-10-29 20:55 ` Milan P. Stanić
2020-10-29 22:21 ` Szabolcs Nagy
2020-10-29 23:00 ` Milan P. Stanić
2020-10-29 23:27 ` Rich Felker
2020-10-30 0:13 ` Rich Felker
2020-10-30 7:47 ` Milan P. Stanić
2020-10-30 18:52 ` Milan P. Stanić
2020-10-30 18:57 ` Rich Felker
2020-10-30 21:31 ` Ariadne Conill
2020-10-31 3:31 ` Rich Felker
2020-11-06 3:36 ` Rich Felker
2020-11-08 16:12 ` Szabolcs Nagy
2020-11-09 17:07 ` Rich Felker
2020-11-09 18:01 ` Érico Nogueira
2020-11-09 18:44 ` Rich Felker
2020-11-09 18:54 ` Érico Nogueira
2020-11-09 21:59 ` Szabolcs Nagy
2020-11-09 22:23 ` Rich Felker
2020-11-11 0:52 ` Rich Felker
2020-11-11 6:35 ` Alexey Izbyshev
2020-11-11 11:25 ` Szabolcs Nagy
2020-11-11 14:56 ` Rich Felker
2020-11-11 16:35 ` Rich Felker
2020-10-31 7:22 ` Timo Teras
2020-10-31 13:29 ` Szabolcs Nagy
2020-10-31 13:35 ` Timo Teras
2020-10-31 14:41 ` Ariadne Conill
2020-10-31 14:49 ` Rich Felker
2020-10-31 14:48 ` Rich Felker
2020-10-31 14:47 ` Rich Felker
2020-10-29 23:32 ` Szabolcs Nagy
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=20201028230610.GA3269@arya.arvanta.net \
--to=mps@arvanta.net \
--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).