public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fweimer at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug dynamic-link/30619] New: Support dlopen after multi-threaded fork in more cases
Date: Thu, 06 Jul 2023 17:24:00 +0000 [thread overview]
Message-ID: <bug-30619-131@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=30619
Bug ID: 30619
Summary: Support dlopen after multi-threaded fork in more cases
Product: glibc
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: dynamic-link
Assignee: unassigned at sourceware dot org
Reporter: fweimer at redhat dot com
Target Milestone: ---
The dlopen function is used internally in various places (backtrace, iconv,
pthread_exit, NSS). It would be preferable if it worked after a multi-threaded
fork.
Right now, we get various hangs, or an assertion failure:
Inconsistency detected by ld.so: dl-open.c: 583: dl_open_worker_begin:
Assertion `r_state == RT_CONSISTENT' failed!
Bug 24941 is an example of a surprising use of NSS. There might be others.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2023-07-06 17:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-06 17:24 fweimer at redhat dot com [this message]
2023-07-06 17:25 ` [Bug dynamic-link/30619] " fweimer at redhat dot com
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=bug-30619-131@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@sourceware.org \
/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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).