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/27646] Linker error for non-existing NSS symbols (e.g. _nss_files_getcanonname_r) from within a dlmopen namespace.
Date: Thu, 17 Jun 2021 13:09:11 +0000	[thread overview]
Message-ID: <bug-27646-131-Epl6QBRYAL@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27646-131@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=27646

Florian Weimer <fweimer at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Target Milestone|---                         |2.34
             Status|ASSIGNED                    |RESOLVED
         Resolution|---                         |FIXED

--- Comment #7 from Florian Weimer <fweimer at redhat dot com> ---
Fixed for glibc 2.34 by:

commit c2059edce20c124d1a99f1a94cc52e83b77a917a
Author: Florian Weimer <fweimer@redhat.com>
Date:   Thu Jun 17 15:06:43 2021 +0200

    elf: Use _dl_catch_error from base namespace in dl-libc.c [BZ #27646]

    dlerrror_run in elf/dl-libc.c needs to call GLRO (dl_catch_error)
    from the base namespace, just like the exported dlerror
    implementation.

    Fixes commit b2964eb1d9a6b8ab1250e8a881cf406182da5875 ("dlfcn:
    Failures after dlmopen should not terminate process [BZ #24772]").

    Reviewed-by: Siddhesh Poyarekar <siddhesh@sourceware.org>

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2021-06-17 13:09 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-24 18:03 [Bug dynamic-link/27646] New: " alfonso.peterssen at oracle dot com
2021-03-31 10:00 ` [Bug dynamic-link/27646] " gilles.m.duboscq at gmail dot com
2021-05-16  3:39 ` evangelos at foutrelis dot com
2021-06-09 11:57 ` mbhangui at gmail dot com
2021-06-09 13:51 ` fweimer at redhat dot com
2021-06-09 13:57 ` fweimer at redhat dot com
2021-06-09 16:45 ` fweimer at redhat dot com
2021-06-14  7:45 ` gilles.m.duboscq at gmail dot com
2021-06-14  8:54 ` fweimer at redhat dot com
2021-06-14  8:55 ` fweimer at redhat dot com
2021-06-14  9:48 ` fweimer at redhat dot com
2021-06-17 13:09 ` fweimer at redhat dot com [this message]
2021-07-02 16:26 ` mbhangui at gmail dot com
2021-07-06 11:14 ` fweimer at redhat dot com
2021-07-06 11:33 ` mbhangui at gmail dot com
2021-07-06 11:47 ` fweimer at redhat dot com
2021-07-06 16:19 ` gilles.m.duboscq at gmail dot com
2021-07-06 16:23 ` fweimer at redhat dot com
2021-12-03 11:03 ` lewurm at gmail 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-27646-131-Epl6QBRYAL@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: 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).