From: Ard Biesheuvel <ard.biesheuvel@linaro.org>
To: M1cha <sigmaepsilon92@gmail.com>
Cc: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
Michael D Kinney <michael.d.kinney@intel.com>,
Liming Gao <liming.gao@intel.com>
Subject: Re: [PATCH 2/3] MdePkg/BaseLib: add attribute 'RETURNS_TWICE' to SetJump
Date: Fri, 22 Dec 2017 15:27:34 +0000 [thread overview]
Message-ID: <CAKv+Gu-pONxtNctr-5g2gxSVi7tk0TPAc5m3PUcp_QiY6P-J0g@mail.gmail.com> (raw)
In-Reply-To: <20171222072336.23504-3-sigmaepsilon92@gmail.com>
On 22 December 2017 at 07:23, M1cha <sigmaepsilon92@gmail.com> wrote:
> When compiling with any ARM toolchain and Os, registers can get
> trashed when returning for the second time from SetJump because GCC
> only handles this correctly when using standard names like 'setjmp' or
> 'getcontext'. When different names are used you have to use the
> attribute 'returns_twice' to tell gcc to be extra careful.
>
> example:
> extern int FN_NAME(void*);
>
> void jmp_buf_set(void *jmpb, void (*f)(void))
> {
> if (!FN_NAME(jmpb))
> f();
> }
>
> this code produces this wrong code with Os:
> 00000000 <jmp_buf_set>:
> 0: e92d4010 push {r4, lr}
> 4: e1a04001 mov r4, r1
> 8: ebfffffe bl 0 <nonstandard_setjmp>
> c: e3500000 cmp r0, #0
> 10: 01a03004 moveq r3, r4
> 14: 08bd4010 popeq {r4, lr}
> 18: 012fff13 bxeq r3
> 1c: e8bd4010 pop {r4, lr}
> 20: e12fff1e bx lr
>
> The generated code pushes backups of r4 and lr to the stack and then
> saves all registers using nonstandard_setjmp.
> Then it pops the stack and jumps to the function in r3 which is the
> main problem because now the function can overwrite our register
> backups on the stack.
> When we return a second time from the call to nonstandard_setjmp, the
> stack pointer has it's original(pushed) position and when the code
> pops r4 and lr from the stack the values are not guaranteed to be the
> same.
>
> When using a standard name like setjmp or getcontext or adding
> '__attribute__((returns_twice))' to nonstandard_setjmp's declaration
> the code looks different:
>
> 00000000 <jmp_buf_set>:
> 0: e92d4007 push {r0, r1, r2, lr}
> 4: e58d1004 str r1, [sp, #4]
> 8: ebfffffe bl 0 <setjmp>
> c: e3500000 cmp r0, #0
> 10: 059d3004 ldreq r3, [sp, #4]
> 14: 01a0e00f moveq lr, pc
> 18: 012fff13 bxeq r3
> 1c: e28dd00c add sp, sp, #12
> 20: e49de004 pop {lr} ; (ldr lr, [sp], #4)
> 24: e12fff1e bx lr
>
> Here the problem is being solved by restoring r3 from the stack
> without popping it.
>
> Contributed-under: TianoCore Contribution Agreement 1.1
> Signed-off-by: Michael Zimmermann <sigmaepsilon92@gmail.com>
Thanks for fixing this. Note that this affects all architectures
targeted by Clang/GCC, not just 32-bit ARM.
Reviewed-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
> ---
> MdePkg/Include/Library/BaseLib.h | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/MdePkg/Include/Library/BaseLib.h b/MdePkg/Include/Library/BaseLib.h
> index 2b98af4cd17e..10976032adaa 100644
> --- a/MdePkg/Include/Library/BaseLib.h
> +++ b/MdePkg/Include/Library/BaseLib.h
> @@ -4905,6 +4905,7 @@ MemoryFence (
> **/
> UINTN
> EFIAPI
> +RETURNS_TWICE
> SetJump (
> OUT BASE_LIBRARY_JUMP_BUFFER *JumpBuffer
> );
> --
> 2.15.1
>
next prev parent reply other threads:[~2017-12-22 15:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-22 7:23 [PATCH 0/3] fix GCC optimizations and warnings for SetJump/LongJump M1cha
2017-12-22 7:23 ` [PATCH 1/3] MdePkg: add RETURNS_TWICE attribute M1cha
2017-12-22 15:24 ` Ard Biesheuvel
2017-12-22 18:27 ` Michael Zimmermann
2017-12-25 3:11 ` Gao, Liming
2017-12-25 15:50 ` Michael Zimmermann
2017-12-26 16:51 ` Gao, Liming
2017-12-26 20:00 ` Michael Zimmermann
2017-12-27 15:56 ` Gao, Liming
2017-12-22 7:23 ` [PATCH 2/3] MdePkg/BaseLib: add attribute 'RETURNS_TWICE' to SetJump M1cha
2017-12-22 15:27 ` Ard Biesheuvel [this message]
2017-12-22 7:23 ` [PATCH 3/3] MdePkg: add NORETURN attribute to LongJump and InternalLongJump M1cha
2017-12-22 15:27 ` Ard Biesheuvel
2017-12-22 17:55 ` [PATCH 0/3] fix GCC optimizations and warnings for SetJump/LongJump Kinney, Michael D
2017-12-22 18:26 ` Michael Zimmermann
2017-12-22 19:01 ` Kinney, Michael D
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-list 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=CAKv+Gu-pONxtNctr-5g2gxSVi7tk0TPAc5m3PUcp_QiY6P-J0g@mail.gmail.com \
--to=devel@edk2.groups.io \
/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