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/31501] New: _dl_tlsdesc_dynamic_xsavec may clobber %rbx Date: Sat, 16 Mar 2024 14:23:18 +0000 [thread overview] Message-ID: <bug-31501-131@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=31501 Bug ID: 31501 Summary: _dl_tlsdesc_dynamic_xsavec may clobber %rbx Product: glibc Version: unspecified Status: NEW Severity: normal Priority: P2 Component: dynamic-link Assignee: fweimer at redhat dot com Reporter: fweimer at redhat dot com Target Milestone: --- Target: x86-64 I believe the stack realignment code in sysdeps/x86_64/dl-tlsdesc-dynamic.h can clobber the initial set of saved registers (including %rbx) if the stack alignment is unfortunate. The stack pointer is aligned down without first decrementing it, so the created stack area can partially overlap with the part of the red zone that was used for the initial register save. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2024-03-16 14:23 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-03-16 14:23 fweimer at redhat dot com [this message] 2024-03-16 14:23 ` [Bug dynamic-link/31501] " fweimer at redhat dot com 2024-03-16 14:35 ` fweimer at redhat dot com 2024-03-16 14:48 ` hjl.tools at gmail dot com 2024-03-16 17:05 ` hjl.tools at gmail dot com 2024-03-17 4:00 ` sam at gentoo dot org 2024-03-17 8:12 ` fweimer at redhat dot com 2024-03-17 10:39 ` hjl.tools at gmail dot com 2024-03-17 10:43 ` sam at gentoo dot org 2024-03-17 10:57 ` sam at gentoo dot org 2024-03-17 16:28 ` hjl.tools at gmail dot com 2024-03-19 2:46 ` cvs-commit at gcc dot gnu.org 2024-03-19 2:46 ` hjl.tools at gmail dot com 2024-03-20 15:37 ` fweimer at redhat dot com 2024-04-02 13:17 ` carlos at redhat dot com 2024-04-03 17:43 ` cvs-commit at gcc dot gnu.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-31501-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).