From: Mark Wielaard <mark@klomp.org>
To: "Dirk Müller" <dirk@dmllr.de>
Cc: elfutils-devel@sourceware.org
Subject: Re: [PATCH] Avoid dlopen on debuginfod-client when not configured
Date: Tue, 29 Mar 2022 09:42:02 +0200 [thread overview]
Message-ID: <YkK4Ss+rpriI8ZKT@wildebeest.org> (raw)
In-Reply-To: <20220328213641.8667-1-dirk@dmllr.de>
Hi Dirk,
On Mon, Mar 28, 2022 at 11:36:41PM +0200, Dirk Müller wrote:
> Loading debuginfod-client is expensive, especially when
> FIPS is enabled, as it goes through time intensive self-checks
> on load.
I assume this is because debuginfod-client loads and initializes
libcurl, which triggers crypto checks for https support?
> Avoid dlopen() when no debuginfo url is set.
The patch itself looks right. But I am slightly afraid this
(theoretically?) will break some programs which set DEBUGINFOD_URLS
themselves. We currently have no other way to make libdwfl use
debuginfod-client. Thoughts?
Cheers,
Mark
> Signed-off-by: Dirk Müller <dirk@dmllr.de>
> ---
> libdwfl/ChangeLog | 5 +++++
> libdwfl/debuginfod-client.c | 12 +++++++++++-
> 2 files changed, 16 insertions(+), 1 deletion(-)
>
> diff --git a/libdwfl/ChangeLog b/libdwfl/ChangeLog
> index 9c5c8517..1ec13f30 100644
> --- a/libdwfl/ChangeLog
> +++ b/libdwfl/ChangeLog
> @@ -1,3 +1,8 @@
> +2022-03-28 Dirk Müller <dirk@dmllr.de>
> +
> + * debuginfod-client.c (__libdwfl_debuginfod_init): Skip dlopen
> + if debuginfod url is unset.
> +
> 2022-02-18 Mark Wielaard <mark@klomp.org>
>
> * image-header.c (__libdw_image_header): Assign header values for
> diff --git a/libdwfl/debuginfod-client.c b/libdwfl/debuginfod-client.c
> index 99b66b6e..af9d1363 100644
> --- a/libdwfl/debuginfod-client.c
> +++ b/libdwfl/debuginfod-client.c
> @@ -101,7 +101,17 @@ __libdwfl_debuginfod_end (debuginfod_client *c)
> void __attribute__ ((constructor))
> __libdwfl_debuginfod_init (void)
> {
> - void *debuginfod_so = dlopen(DEBUGINFOD_SONAME, RTLD_LAZY);
> + void *debuginfod_so;
> +
> + /* Is there any server we can query? If not, don't do any work,
> + just return with ENOSYS. Don't even access the cache. */
> + char *urls_envvar = getenv(DEBUGINFOD_URLS_ENV_VAR);
> + if (urls_envvar == NULL || urls_envvar[0] == '\0')
> + {
> + return;
> + }
> +
> + debuginfod_so = dlopen(DEBUGINFOD_SONAME, RTLD_LAZY);
>
> if (debuginfod_so != NULL)
> {
> --
> 2.35.1
>
next prev parent reply other threads:[~2022-03-29 7:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-28 21:36 Dirk Müller
2022-03-29 7:42 ` Mark Wielaard [this message]
2022-03-29 10:40 ` Frank Ch. Eigler
2022-03-29 11:06 ` Dirk Müller
2022-03-31 12:10 ` Mark Wielaard
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=YkK4Ss+rpriI8ZKT@wildebeest.org \
--to=mark@klomp.org \
--cc=dirk@dmllr.de \
--cc=elfutils-devel@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).