public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "nsz at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug dynamic-link/27072] New: static pie ifunc resolvers run before hwcap is setup Date: Tue, 15 Dec 2020 11:01:02 +0000 [thread overview] Message-ID: <bug-27072-131@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=27072 Bug ID: 27072 Summary: static pie ifunc resolvers run before hwcap is setup Product: glibc Version: 2.32 Status: NEW Severity: normal Priority: P2 Component: dynamic-link Assignee: unassigned at sourceware dot org Reporter: nsz at gcc dot gnu.org Target Milestone: --- as far as i can tell in csu/libc-start.c _dl_relocate_static_pie (); is before _dl_aux_init (auxvec); so ifunc resolvers are run before GL(dl_hwcap) and GL(dl_hwcap2) are set up. on aarch64 this at least affects memory tagging: non-MTE-safe string functions are selected in static PIE binaries unconditionally. but i think this is a bug on all targets where hwcap is passed to ifunc resolvers and support static pie. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2020-12-15 11:01 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-12-15 11:01 nsz at gcc dot gnu.org [this message] 2020-12-15 11:38 ` [Bug dynamic-link/27072] " fweimer at redhat dot com 2021-01-07 12:42 ` 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@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: linkBe 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).