public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "siddhesh at sourceware dot org" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug dynamic-link/27555] Static tests fail with --enable-stack-protector=all Date: Mon, 15 Mar 2021 16:37:31 +0000 [thread overview] Message-ID: <bug-27555-131-tLfZn9QUg1@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-27555-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=27555 Siddhesh Poyarekar <siddhesh at sourceware dot org> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|NEW |RESOLVED --- Comment #1 from Siddhesh Poyarekar <siddhesh at sourceware dot org> --- Fix is in mainline. commit 941ea10f8099cb4fcc98c65249fc17a63fcff6a4 Author: Siddhesh Poyarekar <siddhesh@sourceware.org> Date: Mon Mar 15 20:24:45 2021 +0530 Build get-cpuid-feature-leaf.c without stack-protector [BZ #27555] __x86_get_cpuid_feature_leaf is called during early startup, before the stack check guard is initialized and is hence not safe to build with stack-protector. Additionally, IFUNC resolvers for static tst-ifunc-isa tests get called too early for stack protector to be useful, so fix them to disable stack protector for the resolver functions. This fixes all failures seen with --enable-stack-protector=all configuration. Reviewed-by: Adhemerval Zanella <adhemerval.zanella@linaro.org> I've also created bug 27582 because it is possible (but just a bit more work to vwrite and verify than I can put in at the moment) to make this test non-flaky with stack-protector-all. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2021-03-15 16:37 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-10 10:04 [Bug dynamic-link/27555] New: " siddhesh at sourceware dot org 2021-03-15 16:37 ` siddhesh at sourceware dot org [this message] 2021-03-15 16:37 ` [Bug dynamic-link/27555] " siddhesh at sourceware dot org 2024-06-12 23:22 ` sam at gentoo dot org 2024-06-12 23:22 ` sam at gentoo dot org
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-27555-131-tLfZn9QUg1@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).