public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "stsp at users dot sourceforge.net" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug dynamic-link/30134] DT_AUDIT is ignored for dlopen()ed solib
Date: Sun, 26 Feb 2023 17:09:20 +0000 [thread overview]
Message-ID: <bug-30134-131-Iq9aFUWUt9@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30134-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=30134
--- Comment #13 from Stas Sergeev <stsp at users dot sourceforge.net> ---
(In reply to Jonathon Anderson from comment #12)
> Correct me if I'm wrong, but isn't the solib mapped before DT_AUDIT is read?
See elf/rtld.c:dl_main.
At around line 1844 you see
/* If we have auditing DSOs to load, do it now. */
Then LD_PRELOADs are loaded, then DT_NEEDED.
Then you have la_activity and la_objopen.
So I think auditor is loaded first and that's
intentional.
> So the proposed la_premap wouldn't apply to the solib with the DT_AUDIT,
> only to what it loads and whatever gets loaded later? Which doesn't sound at
> all like what you want.
Well, both parts are not true. :)
It will be applied to the lib being loaded,
AND I want to customize another lib loaded
even later rather than this one.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2023-02-26 17:09 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-17 16:50 [Bug dynamic-link/30134] New: " stsp at users dot sourceforge.net
2023-02-17 19:48 ` [Bug dynamic-link/30134] " fweimer at redhat dot com
2023-02-18 1:17 ` stsp at users dot sourceforge.net
2023-02-18 1:44 ` stsp at users dot sourceforge.net
2023-02-20 11:00 ` fweimer at redhat dot com
2023-02-20 11:50 ` stsp at users dot sourceforge.net
2023-02-20 12:15 ` fweimer at redhat dot com
2023-02-20 12:56 ` stsp at users dot sourceforge.net
2023-02-23 15:58 ` janderson at rice dot edu
2023-02-23 16:02 ` stsp at users dot sourceforge.net
2023-02-26 16:00 ` janderson at rice dot edu
2023-02-26 16:12 ` stsp at users dot sourceforge.net
2023-02-26 16:55 ` janderson at rice dot edu
2023-02-26 17:09 ` stsp at users dot sourceforge.net [this message]
2023-02-26 21:45 ` janderson at rice dot edu
2023-02-27 6:03 ` stsp at users dot sourceforge.net
2023-02-27 6:57 ` janderson at rice dot edu
2023-02-27 7:28 ` stsp at users dot sourceforge.net
2023-02-27 8:16 ` stsp at users dot sourceforge.net
2023-02-27 8:27 ` stsp at users dot sourceforge.net
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-30134-131-Iq9aFUWUt9@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).