public inbox for glibc-cvs@sourceware.org help / color / mirror / Atom feed
From: Florian Weimer <fw@sourceware.org> To: glibc-cvs@sourceware.org Subject: [glibc/release/2.34/master] dlfcn: Pass caller pointer to static dlopen implementation (bug 29446) Date: Thu, 4 Aug 2022 19:55:58 +0000 (GMT) [thread overview] Message-ID: <20220804195558.591BA38582AE@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=875b2414cd68df64aeead651a9b05ae9bc3d88ef commit 875b2414cd68df64aeead651a9b05ae9bc3d88ef Author: Florian Weimer <fweimer@redhat.com> Date: Thu Aug 4 17:54:48 2022 +0200 dlfcn: Pass caller pointer to static dlopen implementation (bug 29446) Fixes commit 0c1c3a771eceec46e66ce1183cf988e2303bd373 ("dlfcn: Move dlopen into libc"). (cherry picked from commit ed0185e4129130cbe081c221efb758fb400623ce) Diff: --- NEWS | 1 + dlfcn/dlopen.c | 2 +- 2 files changed, 2 insertions(+), 1 deletion(-) diff --git a/NEWS b/NEWS index 04fe72b5f6..71a3ab0ed4 100644 --- a/NEWS +++ b/NEWS @@ -112,6 +112,7 @@ The following bugs are resolved with this release: [29211] libc: __open_catalog is not y2038 aware [29213] libc: gconv_parseconfdir is not y2038 aware [29214] nptl: pthread_setcanceltype fails to set type + [29446] _dlopen now ignores dl_caller argument in static mode \f Version 2.34 diff --git a/dlfcn/dlopen.c b/dlfcn/dlopen.c index 9c59c751c4..739d17baaf 100644 --- a/dlfcn/dlopen.c +++ b/dlfcn/dlopen.c @@ -90,7 +90,7 @@ compat_symbol (libdl, ___dlopen, dlopen, GLIBC_2_1); void * __dlopen (const char *file, int mode, void *dl_caller) { - return dlopen_implementation (file, mode, RETURN_ADDRESS (0)); + return dlopen_implementation (file, mode, dl_caller); } void *
reply other threads:[~2022-08-04 19:55 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220804195558.591BA38582AE@sourceware.org \ --to=fw@sourceware.org \ --cc=glibc-cvs@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).