From: Florian Weimer <fweimer@redhat.com>
To: libc-stable@sourceware.org
Subject: Re: [glibc] dlfcn: Implement the RTLD_DI_PHDR request type for dlinfo
Date: Fri, 29 Apr 2022 20:55:36 +0200 [thread overview]
Message-ID: <87tuabzplj.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <20220429155806.594323856DC4@sourceware.org> (Florian Weimer via Glibc-cvs's message of "Fri, 29 Apr 2022 15:58:06 +0000 (GMT)")
* Florian Weimer via Glibc-cvs:
> https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=d056c212130280c0a54d9a4f72170ec621b70ce5
>
> commit d056c212130280c0a54d9a4f72170ec621b70ce5
> Author: Florian Weimer <fweimer@redhat.com>
> Date: Fri Apr 29 17:00:53 2022 +0200
>
> dlfcn: Implement the RTLD_DI_PHDR request type for dlinfo
>
> The information is theoretically available via dl_iterate_phdr as
> well, but that approach is very slow if there are many shared
> objects.
>
> Reviewed-by: Carlos O'Donell <carlos@redhat.com>
> Tested-by: Carlos O'Donell <carlos@rehdat.com>
>
> Diff:
> ---
> dlfcn/Makefile | 4 ++
> dlfcn/dlfcn.h | 7 ++-
> dlfcn/dlinfo.c | 13 ++++-
> dlfcn/tst-dlinfo-phdr.c | 125 ++++++++++++++++++++++++++++++++++++++++++++++++
> manual/dynlink.texi | 15 ++++--
> 5 files changed, 159 insertions(+), 5 deletions(-)
I plan to backport this to 2.35 and 2.34 next week because it
complements the audit fixes.
Thanks,
Florian
parent reply other threads:[~2022-04-29 18:55 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20220429155806.594323856DC4@sourceware.org>]
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=87tuabzplj.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--cc=libc-stable@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).