public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fweimer at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug dynamic-link/27072] static pie ifunc resolvers run before hwcap is setup
Date: Tue, 15 Dec 2020 11:38:39 +0000 [thread overview]
Message-ID: <bug-27072-131-7IXtezMTEK@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27072-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=27072
Florian Weimer <fweimer at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Flags| |security-
CC| |fweimer at redhat dot com
--- Comment #1 from Florian Weimer <fweimer at redhat dot com> ---
Yes, we ran into this on x86 too, where it has been fixed with an artificial
IFUNC relocation (which I think it is inappropriate):
commit 0f09154c64005e78b61484ae87b5ea2028051ea0
Author: H.J. Lu <hjl.tools@gmail.com>
Date: Sat Jul 4 06:35:49 2020 -0700
x86: Initialize CPU info via IFUNC relocation [BZ 26203]
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2020-12-15 11:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-15 11:01 [Bug dynamic-link/27072] New: " nsz at gcc dot gnu.org
2020-12-15 11:38 ` fweimer at redhat dot com [this message]
2021-01-07 12:42 ` [Bug dynamic-link/27072] " hjl.tools at gmail dot com
2021-01-07 14:00 ` nsz at gcc dot gnu.org
2021-01-07 17:10 ` hjl.tools at gmail dot com
2021-01-07 20:33 ` hjl.tools at gmail dot com
2021-01-13 19:20 ` i at maskray dot me
2021-01-19 14:39 ` cvs-commit at gcc dot gnu.org
2021-01-21 15:59 ` cvs-commit at gcc dot gnu.org
2021-01-21 15:59 ` cvs-commit at gcc dot gnu.org
2021-01-21 17:06 ` adhemerval.zanella at linaro dot org
2021-01-21 18:23 ` hjl.tools at gmail dot com
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-27072-131-7IXtezMTEK@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).