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/15271] dlmopen()ed shared library with LM_ID_NEWLM crashes if it fails dlsym() twice Date: Wed, 21 Apr 2021 19:42:26 +0000 [thread overview] Message-ID: <bug-15271-131-ZINooY6bKQ@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-15271-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=15271 Florian Weimer <fweimer at redhat dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|unassigned at sourceware dot org |fweimer at redhat dot com Resolution|--- |FIXED Target Milestone|--- |2.34 Status|WAITING |RESOLVED --- Comment #10 from Florian Weimer <fweimer at redhat dot com> --- Fixed in glibc 2.34 via: commit b2964eb1d9a6b8ab1250e8a881cf406182da5875 Author: Florian Weimer <fweimer@redhat.com> Date: Wed Apr 21 19:49:51 2021 +0200 dlfcn: Failures after dlmopen should not terminate process [BZ #24772] Commit 9e78f6f6e7134a5f299cc8de77370218f8019237 ("Implement _dl_catch_error, _dl_signal_error in libc.so [BZ #16628]") has the side effect that distinct namespaces, as created by dlmopen, now have separate implementations of the rtld exception mechanism. This means that the call to _dl_catch_error from libdl in a secondary namespace does not actually install an exception handler because the thread-local variable catch_hook in the libc.so copy in the secondary namespace is distinct from that of the base namepace. As a result, a dlsym/dlopen/... failure in a secondary namespace terminates the process with a dynamic linker error because it looks to the exception handler mechanism as if no handler has been installed. This commit restores GLRO (dl_catch_error) and uses it to set the handler in the base namespace. Reviewed-by: Adhemerval Zanella <adhemerval.zanella@linaro.org> -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2021-04-21 19:42 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-03-12 17:23 [Bug dynamic-link/15271] New: " brnguyen at nvidia dot com 2013-03-12 20:23 ` [Bug dynamic-link/15271] " carlos at redhat dot com 2013-03-14 23:24 ` brnguyen at nvidia dot com 2013-03-17 17:25 ` carlos at redhat dot com 2013-03-21 0:46 ` brnguyen at nvidia dot com 2013-03-27 4:03 ` carlos at redhat dot com 2013-10-02 22:25 ` neleai at seznam dot cz 2014-06-13 18:42 ` fweimer at redhat dot com 2020-07-23 19:12 ` ajax at redhat dot com 2020-07-23 21:00 ` fweimer at redhat dot com 2020-07-23 21:05 ` fweimer at redhat dot com 2021-04-21 19:42 ` fweimer at redhat dot com [this message] 2021-06-09 13:57 ` fweimer at redhat dot com 2021-06-09 15:17 ` 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-15271-131-ZINooY6bKQ@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).