public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: Florian Weimer via Libc-alpha <libc-alpha@sourceware.org>
Subject: Re: [PATCH] elf: Initialize libc_map to NULL on namespace creation
Date: Fri, 26 Aug 2022 14:49:36 +0200	[thread overview]
Message-ID: <87o7w7p3tr.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <87mtbt5sxi.fsf@oldenburg.str.redhat.com> (Florian Weimer via Libc-alpha's message of "Wed, 24 Aug 2022 21:43:05 +0200")

* Florian Weimer via Libc-alpha:

> It seems that a stale libc_map value will be used (and not
> overwritten) by a dlmopen after a dlclose that has deallocated
> the namespace.  This may not be visible easily because the libc
> link map can be allocated at the same address.
>
> Fixes commit ec935dea6332cb22f9881cd1162bad156173f4b0 ("elf:
> Implement __libc_early_init").

The new version is here:

  [PATCH] elf: Call __libc_early_init for reused namespaces (bug 29528)
  <https://sourceware.org/pipermail/libc-alpha/2022-August/141696.html>

Thanks,
Florian


      reply	other threads:[~2022-08-26 12:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-24 19:43 Florian Weimer
2022-08-26 12:49 ` Florian Weimer [this message]

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=87o7w7p3tr.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).