From: Florian Weimer <fweimer@redhat.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: "H.J. Lu via Libc-alpha" <libc-alpha@sourceware.org>
Subject: Re: [PATCH 1/3] x86: Initialize CPU info via IFUNC relocation [BZ 26203]
Date: Mon, 21 Sep 2020 10:21:30 +0200 [thread overview]
Message-ID: <87imc78rqt.fsf@oldenburg2.str.redhat.com> (raw)
In-Reply-To: <CAMe9rOpzap1NNLZJtbxoJ5rQAdga0OqOw-FpVTC80++Siz-tPQ@mail.gmail.com> (H. J. Lu's message of "Fri, 18 Sep 2020 07:30:16 -0700")
* H. J. Lu:
>> Putting this data into _rtld_global_ro is not correct if it is required
>> after static dlopen. The current static dlopen approach simply does not
>> support that. You can only assume that libc.so has been initialized
>> after static dlopen.
> Unless it is removed, _rtld_global_ro is the right place. _rtld_global_ro
> is initialized by dynamic relocation. My patch does it.
It initializes only part of it. I find this rather confusing.
Why is this data in ld.so in the first place?
Thanks,
Florian
--
Red Hat GmbH, https://de.redhat.com/ , Registered seat: Grasbrunn,
Commercial register: Amtsgericht Muenchen, HRB 153243,
Managing Directors: Charles Cachera, Brian Klemm, Laurie Krebs, Michael O'Neill
next prev parent reply other threads:[~2020-09-21 8:21 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-12 13:44 [PATCH 0/3] ld.so: Add --list-tunables to print tunable values H.J. Lu
2020-09-12 13:44 ` [PATCH 1/3] x86: Initialize CPU info via IFUNC relocation [BZ 26203] H.J. Lu
2020-09-18 8:06 ` Florian Weimer
2020-09-18 13:55 ` H.J. Lu
2020-09-18 13:59 ` Florian Weimer
2020-09-18 14:18 ` H.J. Lu
2020-09-18 14:22 ` Florian Weimer
2020-09-18 14:30 ` H.J. Lu
2020-09-21 8:21 ` Florian Weimer [this message]
2020-09-21 11:31 ` H.J. Lu
2020-09-25 12:55 ` Florian Weimer
2020-09-12 13:44 ` [PATCH 2/3] Set tunable value as well as min/max values H.J. Lu
2020-09-18 8:29 ` Florian Weimer
2020-09-18 15:11 ` H.J. Lu
2020-09-12 13:44 ` [PATCH 3/3] ld.so: Add --list-tunables to print tunable values H.J. Lu
2020-09-18 8:13 ` Florian Weimer
2020-09-18 15:24 ` H.J. Lu
-- strict thread matches above, loose matches on Subject: below --
2020-07-12 14:24 [PATCH 0/3] " H.J. Lu
2020-07-12 14:24 ` [PATCH 1/3] x86: Initialize CPU info via IFUNC relocation [BZ 26203] H.J. Lu
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=87imc78rqt.fsf@oldenburg2.str.redhat.com \
--to=fweimer@redhat.com \
--cc=hjl.tools@gmail.com \
--cc=libc-alpha@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).