From: Mathieu Desnoyers via Libc-alpha <libc-alpha@sourceware.org>
To: Florian Weimer <fw@deneb.enyo.de>
Cc: libc-alpha@sourceware.org
Subject: Re: [PATCH] elf: Add initial flag argument to __libc_early_init
Date: Mon, 27 Apr 2020 14:07:44 -0400 [thread overview]
Message-ID: <20200427180744.btytgboc6eeswaal@localhost> (raw)
On 27-Apr-2020 12:31:21 PM, Florian Weimer wrote:
[...]
> diff --git a/elf/dl-open.c b/elf/dl-open.c
> index ac7ab495e4..7bf1144e93 100644
> --- a/elf/dl-open.c
> +++ b/elf/dl-open.c
> @@ -748,9 +748,22 @@ dl_open_worker (void *a)
> LIBC_PROBE (reloc_complete, 3, args->nsid, r, new);
>
> /* If libc.so was not there before, attempt to call its early
> - initialization routine. */
> + initialization routine. Indicate to the initialization routine
> + whether thie libc being initialized is the one in the base
thie -> the
> + namespace. */
> if (!args->libc_already_loaded)
> - _dl_call_libc_early_init (GL(dl_ns)[args->nsid].libc_map);
> + {
> + struct link_map *libc_map = GL(dl_ns)[args->nsid].libc_map;
> +#ifdef SHARED
> + bool initial = libc_map->l_ns == LM_ID_BASE;
> +#else
> + /* In the static case, there is only one namespace, but it
> + contains a secondary libc (the primary libc is statically
> + linked). */
This comment seems misaligned.
Thanks,
Mathieu
--
Mathieu Desnoyers
EfficiOS Inc.
http://www.efficios.com
next reply other threads:[~2020-04-27 18:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-27 18:07 Mathieu Desnoyers via Libc-alpha [this message]
2020-04-27 19:06 ` [PATCH] elf: Add initial flag argument to __libc_early_init Florian Weimer
-- strict thread matches above, loose matches on Subject: below --
2020-04-27 12:31 Florian Weimer
2020-04-29 13:30 ` Carlos O'Donell via Libc-alpha
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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200427180744.btytgboc6eeswaal@localhost \
--to=libc-alpha@sourceware.org \
--cc=fw@deneb.enyo.de \
--cc=mathieu.desnoyers@efficios.com \
/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).