public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Gao, Liming" <liming.gao@intel.com>
To: M1cha <sigmaepsilon92@gmail.com>,
	"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>,
	"Kinney, Michael D" <michael.d.kinney@intel.com>
Subject: Re: [PATCH v3 2/3] MdePkg/BaseLib: add attribute 'RETURNS_TWICE' to SetJump
Date: Mon, 8 Jan 2018 05:34:55 +0000	[thread overview]
Message-ID: <4A89E2EF3DFEDB4C8BFDE51014F606A14E1A023C@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <20180107173103.29032-1-sigmaepsilon92@gmail.com>

Reviewed-by: Liming Gao <liming.gao@intel.com>

>-----Original Message-----
>From: M1cha [mailto:sigmaepsilon92@gmail.com]
>Sent: Monday, January 08, 2018 1:31 AM
>To: edk2-devel@lists.01.org
>Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>; Kinney, Michael D
><michael.d.kinney@intel.com>; Gao, Liming <liming.gao@intel.com>
>Subject: [edk2] [PATCH v3 2/3] MdePkg/BaseLib: add attribute
>'RETURNS_TWICE' to SetJump
>
>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>
>---
> MdePkg/Include/Library/BaseLib.h             | 1 +
> MdePkg/Library/BaseLib/Ebc/SetJumpLongJump.c | 1 +
> MdePkg/Library/BaseLib/Ia32/SetJump.c        | 1 +
> 3 files changed, 3 insertions(+)
>
>diff --git a/MdePkg/Include/Library/BaseLib.h
>b/MdePkg/Include/Library/BaseLib.h
>index 05eb4e33a086..39573db0c8da 100644
>--- a/MdePkg/Include/Library/BaseLib.h
>+++ b/MdePkg/Include/Library/BaseLib.h
>@@ -4903,6 +4903,7 @@ MemoryFence (
>   @retval 0 Indicates a return from SetJump().
>
> **/
>+RETURNS_TWICE
> UINTN
> EFIAPI
> SetJump (
>diff --git a/MdePkg/Library/BaseLib/Ebc/SetJumpLongJump.c
>b/MdePkg/Library/BaseLib/Ebc/SetJumpLongJump.c
>index 4c0dba55d52f..683527a36fda 100644
>--- a/MdePkg/Library/BaseLib/Ebc/SetJumpLongJump.c
>+++ b/MdePkg/Library/BaseLib/Ebc/SetJumpLongJump.c
>@@ -32,6 +32,7 @@
>   @retval 0 Indicates a return from SetJump().
>
> **/
>+RETURNS_TWICE
> UINTN
> EFIAPI
> SetJump (
>diff --git a/MdePkg/Library/BaseLib/Ia32/SetJump.c
>b/MdePkg/Library/BaseLib/Ia32/SetJump.c
>index 304f3839b108..652d45d53ba7 100644
>--- a/MdePkg/Library/BaseLib/Ia32/SetJump.c
>+++ b/MdePkg/Library/BaseLib/Ia32/SetJump.c
>@@ -49,6 +49,7 @@ InternalAssertJumpBuffer (
>
> **/
> _declspec (naked)
>+RETURNS_TWICE
> UINTN
> EFIAPI
> SetJump (
>--
>2.15.1



      reply	other threads:[~2018-01-08  5:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-07 17:31 [PATCH v3 2/3] MdePkg/BaseLib: add attribute 'RETURNS_TWICE' to SetJump M1cha
2018-01-08  5:34 ` Gao, Liming [this message]

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=4A89E2EF3DFEDB4C8BFDE51014F606A14E1A023C@SHSMSX104.ccr.corp.intel.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