Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 21 May 2023 06:28:48 +0000
From:      bugzilla-noreply@freebsd.org
To:        threads@FreeBSD.org
Subject:   [Bug 271490] Deadlock between _rtld_atfork_pre and _thr_attr_init
Message-ID:  <bug-271490-13406-p33lrr1O2j@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-271490-13406@https.bugs.freebsd.org/bugzilla/>
References:  <bug-271490-13406@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D271490

--- Comment #12 from KJ Tsanaktsidis <kj@kjtsanaktsidis.id.au> ---
Yes - https://reviews.freebsd.org/D40178 seems to fix the issue with running
the ruby tests. I applied it on top of the `releng/13.2` branch on my system
and followed the  I've been running the test in question for half an hour i=
n a
loop and no failures yet!

Thanks so much for your help debugging this. I must say - this has been my
first experience with anything in BSD-world, and I've really appreciated ha=
ving
the source for the base system all in one giant git repo together. Makes it
easy to go spelunking and understand how it all fits together. As someone w=
ho
recently spent many hours staring at #ifdef soup across glibc, libgcc_s, and
the Linux kernel recently, it's been very refreshing!

I don't really know how the backport process works - is your intention to
backport this to 13.1/13.2 or would the fix just apply from 13.3 forward? If
there's no backport I'll probably add `LD_BIND_NOW=3Dyes` to the Ruby test =
runner
for FreeBSD <=3D 13.2 - does this seem reasonable?

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-271490-13406-p33lrr1O2j>