public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "al_95 at outlook dot it" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug dynamic-link/29600] New: dlmopen hangs after loading certain libraries Date: Thu, 22 Sep 2022 14:33:12 +0000 [thread overview] Message-ID: <bug-29600-131@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=29600 Bug ID: 29600 Summary: dlmopen hangs after loading certain libraries Product: glibc Version: 2.36 Status: UNCONFIRMED Severity: normal Priority: P2 Component: dynamic-link Assignee: unassigned at sourceware dot org Reporter: al_95 at outlook dot it Target Milestone: --- Created attachment 14351 --> https://sourceware.org/bugzilla/attachment.cgi?id=14351&action=edit dlmopen test Hi. I discovered a regression bug in dlmopen introduced with the fix to bug 29528. Certain libraries seem to leave the dynamic loader namespaces in an inconsistent state, causing all subsequent dlmopen calls to hang. The hang happens at the for loop inside the _dl_debug_initialize function in dl-open.c, when it iterates through the namespaces linked list. This issue happens only after loading certain libraries, but not others. I attached a small program that exhibits this issue on my pc. After libcurl is loaded (and unloaded) any following call to dlmopen will freeze. Moving the order around doesn't change much, except when libcurl is loaded first, then somehow everything works. A few other libraries I tested that cause this behavior are libstdc++, libavcodec and libssl, but there are probably more. The issue appeared with commit 924e4f3eaa502ce82fccf8537f021a796d158771 (and the correlated d0e357ff45a75553dee3b17ed7d303bfa544f6fe) and is still present in the latest commit (de477abcaaabb1f9815cb63876637a47a95e7ac1). According to the messages in bug 29528, the changes were also applied to version 2.35 and 2.34, so it's possible those are broken too. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2022-09-22 14:33 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-09-22 14:33 al_95 at outlook dot it [this message] 2022-09-22 14:56 ` [Bug dynamic-link/29600] " fweimer at redhat dot com 2022-09-22 14:58 ` fweimer at redhat dot com 2022-09-22 18:06 ` fweimer at redhat dot com 2022-10-14 9:08 ` 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-29600-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: linkBe 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).