public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "conanhc at gmail dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug dynamic-link/25615] dlopen RTLD_NOLOAD optimization Date: Wed, 13 Mar 2024 20:27:56 +0000 [thread overview] Message-ID: <bug-25615-131-sFp4HGorJs@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-25615-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=25615 Conan Huang <conanhc at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |INVALID --- Comment #2 from Conan Huang <conanhc at gmail dot com> --- Optimization breaks following scenario: If we dlopen(library, RTLD_NOLOAD | RTLD_LAZY). If that library doesn't have its local search scope already set up (l_local_scope). Then dlopen will set it up by calling _dl_map_object_deps and going thru its dependencies. With NOLOAD optimization patch, it'll skip _dl_map_object_deps, and not setup l_local_scope. If we call dlsym after dlopen(library, RTLD_NOLOAD), dynamic loader tries to search that library's local scope for a definition. If l_local_scope is empty, dynamic loader will segfault. As a result, _dl_map_object_deps is needed to generate l_local_scope. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2024-03-13 20:27 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-25615-131@http.sourceware.org/bugzilla/> 2020-03-30 16:47 ` carlos at redhat dot com 2024-03-13 20:27 ` conanhc at gmail dot com [this message] 2024-03-14 10:09 ` 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-25615-131-sFp4HGorJs@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).