public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug dynamic-link/29528] __libc_early_init not called after dlmopen that reuses namespace Date: Fri, 14 Oct 2022 10:37:51 +0000 [thread overview] Message-ID: <bug-29528-131-iGXmyaAZh8@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-29528-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=29528 --- Comment #6 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> --- The release/2.35/master branch has been updated by Florian Weimer <fw@sourceware.org>: https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=8d125a1f9145ad90c94e438858d6b5b7578686f2 commit 8d125a1f9145ad90c94e438858d6b5b7578686f2 Author: Florian Weimer <fweimer@redhat.com> Date: Fri Oct 14 11:02:25 2022 +0200 elf: Do not completely clear reused namespace in dlmopen (bug 29600) The data in the _ns_debug member must be preserved, otherwise _dl_debug_initialize enters an infinite loop. To be conservative, only clear the libc_map member for now, to fix bug 29528. Fixes commit d0e357ff45a75553dee3b17ed7d303bfa544f6fe ("elf: Call __libc_early_init for reused namespaces (bug 29528)"), by reverting most of it. Reviewed-by: Carlos O'Donell <carlos@redhat.com> Tested-by: Carlos O'Donell <carlos@redhat.com> (cherry picked from commit 2c42257314536b94cc8d52edede86e94e98c1436) -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2022-10-14 10:37 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-08-26 11:22 [Bug dynamic-link/29528] New: __libc_early_init not called after dlmopen fweimer at redhat dot com 2022-08-26 11:22 ` [Bug dynamic-link/29528] " fweimer at redhat dot com 2022-08-26 11:26 ` [Bug dynamic-link/29528] __libc_early_init not called after dlmopen that reuses namespace fweimer at redhat dot com 2022-08-26 13:52 ` fweimer at redhat dot com 2022-08-26 19:45 ` fweimer at redhat dot com 2022-08-29 13:47 ` fweimer at redhat dot com 2022-09-22 14:39 ` al_95 at outlook dot it 2022-09-22 14:58 ` fweimer at redhat dot com 2022-10-14 9:02 ` cvs-commit at gcc dot gnu.org 2022-10-14 9:29 ` cvs-commit at gcc dot gnu.org 2022-10-14 10:37 ` cvs-commit at gcc dot gnu.org [this message] 2022-10-14 11:03 ` cvs-commit at gcc dot gnu.org
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-29528-131-iGXmyaAZh8@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).