From: Ammar Faizi <[email protected]>
To: Zhangjin Wu <[email protected]>
Cc: "Willy Tarreau" <[email protected]>,
"Thomas Weißschuh" <[email protected]>,
"Ammar Faizi" <[email protected]>,
"Nicholas Rosenberg" <[email protected]>,
"GNU/Weeb Mailing List" <[email protected]>,
"Michael William Jonathan" <[email protected]>,
"Linux Kernel Mailing List" <[email protected]>
Subject: Re: [PATCH v1 1/1] tools/nolibc: i386: Fix a stack misalign bug on _start
Date: Sat, 26 Aug 2023 22:55:07 +0700 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On Sat, Aug 26, 2023 at 11:07:04PM +0800, Zhangjin Wu wrote:
> > @@ -167,7 +167,8 @@ void __attribute__((weak, noreturn, optimize("Os", "omit-frame-pointer"))) __no_
> > __asm__ volatile (
> > "xor %ebp, %ebp\n" /* zero the stack frame */
> > "mov %esp, %eax\n" /* save stack pointer to %eax, as arg1 of _start_c */
> > - "and $-16, %esp\n" /* last pushed argument must be 16-byte aligned */
> > + "and $-16, %esp\n" /* align stack to 16 bytes */
> > + "sub $12, %esp\n" /* last pushed argument must be 16-byte aligned */
>
> Ammar, the new call of _start_c() only requires a single push, it pushes
> the argument and minus %esp by 4, so, the alignment of %esp requires to
> minus 12 to reserve 16-byte alignment, is this description right?
Yes, that's correct.
> If so, What about further?
>
> "and $-16, %esp\n" /* align stack to 16 bytes */
> "sub ($16 - $4), %esp" /* the 'push %eax' breaks stack alignment, fix up it */
The sub part should have been:
"sub $(16 - 4), %esp\n"
It's fine to me writing it that way too.
--
Ammar Faizi
next prev parent reply other threads:[~2023-08-26 15:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-26 14:16 [PATCH v1 0/1] Fix a stack misalign bug on _start Ammar Faizi
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 [this message]
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 \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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