Date: Thu, 18 May 2023 17:44:25 +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-Y0gMtP2Eg9@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=271490 Konstantin Belousov <kib@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kib@FreeBSD.org --- Comment #1 from Konstantin Belousov <kib@FreeBSD.org> --- Yes, this is indeed a bug in jemalloc. It seems that the problem is that malloc_mutex_prefork() from jemalloc/src/mutex.c does not lock _all_ jemalloc mutexes, in particular, the extent mtx. OTOH, note that after fork(), in multi-threaded process child, only async-signal safe functions are guaranteed to work. -- 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-Y0gMtP2Eg9>