From: Florian Weimer <fweimer@redhat.com>
To: Florian Weimer via Libc-alpha <libc-alpha@sourceware.org>
Subject: Re: [PATCH] elf: Do not completely clear reused namespace in dlmopen (bug 29600)
Date: Tue, 11 Oct 2022 09:54:39 +0200 [thread overview]
Message-ID: <87czayhk1s.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <87pmfn1ftc.fsf@oldenburg.str.redhat.com> (Florian Weimer via Libc-alpha's message of "Thu, 22 Sep 2022 19:26:07 +0200")
* Florian Weimer via Libc-alpha:
> 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.
>
> Tested on i686-linux-gnu and x86_64-linux-gnu.
Ping. This patch needs review:
<https://sourceware.org/pipermail/libc-alpha/2022-September/142199.html>
Thanks,
Florian
next prev parent reply other threads:[~2022-10-11 7:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-22 17:26 Florian Weimer
2022-10-11 7:54 ` Florian Weimer [this message]
2022-10-13 20:45 ` Carlos O'Donell
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=87czayhk1s.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--cc=libc-alpha@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).