From: Ammar Faizi <ammarfaizi2@gnuweeb.org>
To: "Willy Tarreau" <w@1wt.eu>, "Thomas Weißschuh" <linux@weissschuh.net>
Cc: Ammar Faizi <ammarfaizi2@gnuweeb.org>,
Zhangjin Wu <falcon@tinylab.org>,
Nicholas Rosenberg <inori@vnlx.org>,
GNU/Weeb Mailing List <gwml@vger.gnuweeb.org>,
Michael William Jonathan <moe@gnuweeb.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [PATCH v1 0/1] Fix a stack misalign bug on _start
Date: Sat, 26 Aug 2023 21:16:31 +0700 [thread overview]
Message-ID: <20230826141632.1488740-1-ammarfaizi2@gnuweeb.org> (raw)
Hi Willy,
Just a single quick fix.
The ABI mandates that the %esp register must be a multiple of 16 when
executing a call instruction.
Commit 2ab446336b17 simplified the _start function, but it didn't take
care of the %esp alignment, causing SIGSEGV on SSE and AVX programs that
use aligned move instruction (e.g., movdqa, movaps, and vmovdqa).
$eax : 0x56559000 → 0x00003f90
$ebx : 0x56559000 → 0x00003f90
$ecx : 0x1
$edx : 0xf7fcaaa0 → endbr32
$esp : 0xffffcdbc → 0x00000001
$ebp : 0x0
$esi : 0xffffce7c → 0xffffd096
$edi : 0x56556060 → <_start+0> xor %ebp, %ebp
$eip : 0x56556489 → <sse_pq_add+25> movaps %xmm0, 0x30(%esp)
<sse_pq_add+11> pop %eax
<sse_pq_add+12> add $0x2b85, %eax
<sse_pq_add+18> movups -0x1fd0(%eax), %xmm0
→ <sse_pq_add+25> movaps %xmm0, 0x30(%esp) <== trapping instruction
<sse_pq_add+30> movups -0x1fe0(%eax), %xmm1
<sse_pq_add+37> movaps %xmm1, 0x20(%esp)
<sse_pq_add+42> movups -0x1ff0(%eax), %xmm2
<sse_pq_add+49> movaps %xmm2, 0x10(%esp)
<sse_pq_add+54> movups -0x2000(%eax), %xmm3
[#0] Id 1, Name: "test", stopped 0x56556489 in sse_pq_add (), reason: SIGSEGV
(gdb) bt
#0 0x56556489 in sse_pq_add ()
#1 0x5655608e in main ()
Ensure the %esp is a multiple of 16 when executing the call instruction.
Signed-off-by: Ammar Faizi <ammarfaizi2@gnuweeb.org>
---
Ammar Faizi (1):
tools/nolibc: i386: Fix a stack misalign bug on _start
tools/include/nolibc/arch-i386.h | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
base-commit: 6269320850097903b30be8f07a5c61d9f7592393
--
Ammar Faizi
next reply other threads:[~2023-08-26 14:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-26 14:16 Ammar Faizi [this message]
2023-08-26 14:16 ` [PATCH v1 1/1] tools/nolibc: i386: " Ammar Faizi
2023-08-26 15:07 ` Zhangjin Wu
2023-08-26 15:55 ` Ammar Faizi
2023-08-27 6:53 ` Thomas Weißschuh
2023-08-27 7:22 ` Ammar Faizi
2023-08-26 15:20 ` [PATCH v1 0/1] " Zhangjin Wu
2023-08-26 16:04 ` Ammar Faizi
2023-08-26 16:36 ` Zhangjin Wu
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=20230826141632.1488740-1-ammarfaizi2@gnuweeb.org \
--to=ammarfaizi2@gnuweeb.org \
--cc=falcon@tinylab.org \
--cc=gwml@vger.gnuweeb.org \
--cc=inori@vnlx.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@weissschuh.net \
--cc=moe@gnuweeb.org \
--cc=w@1wt.eu \
/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
all inboxes | Powered by JetHome®