public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "keno at juliacomputing dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug dynamic-link/29446] New: __dlopen now ignores dl_caller argument
Date: Thu, 04 Aug 2022 04:43:20 +0000 [thread overview]
Message-ID: <bug-29446-131@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=29446
Bug ID: 29446
Summary: __dlopen now ignores dl_caller argument
Product: glibc
Version: 2.34
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: dynamic-link
Assignee: unassigned at sourceware dot org
Reporter: keno at juliacomputing dot com
Target Milestone: ---
In commit 0c1c3a77 ("dlfcn: Move dlopen into libc"),
the previous __dlopen symbol was renamed dlopen_implementation,
and moved into libc. After this commit, __dlopen is now:
```
void *
__dlopen (const char *file, int mode, void *dl_caller)
{
return dlopen_implementation (file, mode, RETURN_ADDRESS (0));
}
```
This seems like it may be a bug, because the `dl_caller`
argument to `__dlopen` is now ignored. I don't have a concrete
case where this causes any problems, this was just noticed by
inspection, but it looked wrong.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2022-08-04 4:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-04 4:43 keno at juliacomputing dot com [this message]
2022-08-04 6:24 ` [Bug dynamic-link/29446] " fweimer at redhat dot com
2022-08-04 6:25 ` [Bug dynamic-link/29446] __dlopen now ignores dl_caller argument in static mode fweimer at redhat dot com
2022-08-04 6:51 ` fweimer at redhat 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-29446-131@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).