public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <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 21:13:19 +0000 [thread overview]
Message-ID: <bug-31877-131-UQ93gq9OJO@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31877-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=31877
--- Comment #4 from H.J. Lu <hjl.tools at gmail dot com> ---
(In reply to Sam James from comment #3)
> ```
> # GLIBC_TUNABLES=glibc.cpu.hwcaps=SHSTK elf/tst-shstk-legacy-1g ; echo $?
> Expected signal 'Segmentation fault' from child, got none
> 1
> ```
This sounds like a kernel or CPU bug:
(gdb) b legacy
Function "legacy" not defined.
Make breakpoint pending on future shared library load? (y or [n]) y
Breakpoint 1 (legacy) pending.
(gdb) r
Starting program:
/export/build/gnu/tools-build/glibc-cet-gitlab/build-x86_64-linux/elf/tst-shstk-legacy-1g
warning: Unable to find libthread_db matching inferior's thread library, thread
debugging will not be available.
Breakpoint 1, legacy () at ../sysdeps/x86_64/tst-shstk-legacy-1-extra.S:25
25 movq (%rsp), %rax
(gdb) disass
Dump of assembler code for function legacy:
=> 0x000055555554e0f9 <+0>: mov (%rsp),%rax
0x000055555554e0fd <+4>: add $0x8,%rsp
0x000055555554e101 <+8>: jmp *%rax <<< Shadow srack isn't popped.
End of assembler dump.
(gdb) bt
#0 legacy () at ../sysdeps/x86_64/tst-shstk-legacy-1-extra.S:25
#1 0x00007ffff7fcb2de in call_init (l=<optimized out>, argc=1,
argv=0x7fffffffdd68, env=0x7fffffffdd78) at dl-init.c:74
#2 call_init (l=<optimized out>, argc=1, argv=0x7fffffffdd68,
env=0x7fffffffdd78) at dl-init.c:26
#3 0x00007ffff7fcb3cc in _dl_init (main_map=0x7ffff7ffe2e0, argc=1,
argv=0x7fffffffdd68, env=0x7fffffffdd78) at dl-init.c:121
#4 0x00007ffff7fe32a0 in _dl_start_user ()
from
/export/build/gnu/tools-build/glibc-cet-gitlab/build-x86_64-linux/elf/ld.so
#5 0x0000000000000001 in ?? ()
#6 0x00007fffffffe0cb in ?? ()
#7 0x0000000000000000 in ?? ()
(gdb) c
Continuing.
Program received signal SIGSEGV, Segmentation fault.
0x00007ffff7fcb2ee in call_init (l=<optimized out>, argc=<optimized out>,
argv=<optimized out>, env=<optimized out>) at dl-init.c:76
76 } <<< Shadow stack mismatch.
(gdb)
[hjl@gnu-tgl-3 libgcc]$ ps xa | grep legacy
822317 pts/0 Sl+ 0:00 gdb elf/tst-shstk-legacy-1g
822327 pts/0 t 0:00
/export/build/gnu/tools-build/glibc-cet-gitlab/build-x86_64-linux/elf/tst-shstk-legacy-1g
822373 pts/2 S+ 0:00 grep --color=auto legacy
[hjl@gnu-tgl-3 libgcc]$ grep features /proc/822327/status
x86_Thread_features: shstk
x86_Thread_features_locked: shstk wrss
[hjl@gnu-tgl-3 libgcc]$
Please check if SHSTK is enabled.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2024-06-10 21:13 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 ` [Bug libc/31877] " sam at gentoo dot org
2024-06-10 20:49 ` 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 [this message]
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-UQ93gq9OJO@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).