public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "janderson at rice dot edu" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug dynamic-link/30134] DT_AUDIT is ignored for dlopen()ed solib
Date: Thu, 23 Feb 2023 15:58:01 +0000	[thread overview]
Message-ID: <bug-30134-131-PVtZw55toX@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30134-131@http.sourceware.org/bugzilla/>

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

Jonathon Anderson <janderson at rice dot edu> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |janderson at rice dot edu

--- Comment #8 from Jonathon Anderson <janderson at rice dot edu> ---
(In reply to Stas Sergeev from comment #7)
> (In reply to Florian Weimer from comment #6)
> > If the auditor cannot intercept libc.so.6 calls because it is already
> > loaded, then it can even use the main libc.so.6, and no fully separate
> > namespace is needed at all.
> 
> Certainly I don't know the implications,
> but in all projects where I needed to
> intercept the glibc calls I was using
> LD_PRELOAD (or the more advanced techniques
> like dlmopen() the libc into another
> namespace and intercept it there), but
> not LD_AUDIT. I've yet to understand is
> there something special in those complex
> pltenter/pltexit call-backs that you can't
> do by some other means, and are there
> many/any users of them?

pltenter/pltexit allows you to wrap symbols without knowing the signature of
the wrapped function. AFAIK there isn't a way to write a function that does
that in standard or GNU C (...without writing straight assembly based on the
call ABI, not fun).

That said, I don't personally know any users besides sotruss, one of the Glibc
dev tools. So do with that what you will. :D

> But having audit modules in the main
> namespace would help me a lot.

My group relies on LD_AUDIT to reliably "escape" the main namespace and acquire
symbols that won't be overridden by any other in-process tools operating at the
same time. Merging those namespaces will cause us some significant grief.

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

  parent reply	other threads:[~2023-02-23 15:58 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 [this message]
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
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-PVtZw55toX@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).