public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "sam at gentoo dot org" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug libc/31877] elf/tst-shstk-legacy-1g test failure on znver4 Date: Mon, 10 Jun 2024 19:44:04 +0000 [thread overview] Message-ID: <bug-31877-131-gDtrbemr4n@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-31877-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=31877 Sam James <sam at gentoo dot org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |simon.chopin at canonical dot com --- Comment #1 from Sam James <sam at gentoo dot org> --- Ubuntu seem to have hit this too at https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/2059603 (Simon, was it on znver3/znver4, or Intel HW?) ``` # zgrep -Ei "(ibt|shstk|cet)=" /proc/config.gz CONFIG_CC_HAS_IBT=y CONFIG_X86_CET=y CONFIG_X86_KERNEL_IBT=y ``` ``` # uname -a Linux goop 6.9.3 #1 SMP PREEMPT_DYNAMIC Thu Jun 6 10:29:40 BST 2024 x86_64 AMD Ryzen 9 PRO 7940HS w/ Radeon 780M Graphics AuthenticAMD GNU/Linux ``` -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2024-06-10 19:44 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-06-10 19:42 [Bug libc/31877] New: " sam at gentoo dot org 2024-06-10 19:44 ` sam at gentoo dot org [this message] 2024-06-10 20:49 ` [Bug libc/31877] " hjl.tools at gmail dot com 2024-06-10 20:51 ` sam at gentoo dot org 2024-06-10 21:13 ` hjl.tools at gmail dot com 2024-06-18 13:12 ` simon.chopin at canonical 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-31877-131-gDtrbemr4n@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).