Skip to contentSkip to conversation

arm64: Large PIE fixes

PATCH New Edgar E. Iglesias 7 participants 14 messages Sep 9, 2020 – Sep 14, 2020 Arm (32-bit)

lore
Share & tools
lore
#0 lore raw

v3 cover arm64: Large PIE fixes

From: "Edgar E. Iglesias" <[email protected]>

This fixes some build issues with large (> 1MB) PIE U-Boot setups. We also document the 4K aligned load address requirement and add an early run-time check for it.

As requested by reviewers, I've also added a runtime check for non-PIE builds to trap the startup sequence early if the start address doesn't match between run-time and link-time.

Cheers,
Edgar

ChangeLog:
v2 -> v3:
* Add non-PIE start address (run vs link-time) check
* Move 4K aligment Kconfig help description
* Fix load of __bss_start
* Use x0 rather than x1 in PIE load-address check
* Add missing tabs
* Add load-address check for non-PIE
* U-boot -> U-Boot in a few places
* Tweak commit messages

v1 -> v2:
* Fix adr of _start in arch/arm/lib/crt0_64.S
* Add early check and bail out into a WFI loop when not 4K aligned
* Document the 4K alignement requirement in Kconfig

Edgar E. Iglesias (4):
arm64: Mention 4K aligned load addresses in the PIE Kconfig help
arm64: Trap PIE builds early if load address is not 4K aligned
arm64: Add support for larger PIE U-Boot
arm64: Trap non-PIE builds early if starting from wrong address

 arch/arm/Kconfig           |  4 ++--
 arch/arm/cpu/armv8/start.S | 36 ++++++++++++++++++++++++++++++++++--
 arch/arm/lib/crt0_64.S     |  8 +++++++-
 3 files changed, 43 insertions(+), 5 deletions(-)
Signature · 1 line
2.25.1
#1 lore raw

PATCH v3 1/4 arm64: Mention 4K aligned load addresses in the PIE Kconfig help

From: "Edgar E. Iglesias" <[email protected]>

Mention the requirement of 4K aligned load addresses in the help section for the POSITION_INDEPENDENT option.

---
 arch/arm/Kconfig | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
arch/arm/Kconfig +2 -2
index 80702c23d3..67286e8b5d 100644
@@ -16,8 +16,8 @@ config POSITION_INDEPENDENT
 	help
 	  U-Boot expects to be linked to a specific hard-coded address, and to
 	  be loaded to and run from that address. This option lifts that
-	  restriction, thus allowing the code to be loaded to and executed
-	  from almost any address. This logic relies on the relocation
+	  restriction, thus allowing the code to be loaded to and executed from
+	  almost any 4K aligned address. This logic relies on the relocation
 	  information that is embedded in the binary to support U-Boot
 	  relocating itself to the top-of-RAM later during execution.
 
Signature · 1 line
2.25.1
#2 lore raw

PATCH v3 2/4 arm64: Trap PIE builds early if load address is not 4K aligned

In reply to Edgar E. Iglesias

From: "Edgar E. Iglesias" <[email protected]>

PIE requires a 4K aligned load address. If this is not met, trap the startup sequence in a WFI loop rather than running into obscure failures.

---
 arch/arm/cpu/armv8/start.S | 17 +++++++++++++++++
 1 file changed, 17 insertions(+)
arch/arm/cpu/armv8/start.S +17 -0
index 002698b501..85baebc5f7 100644
@@ -59,6 +59,23 @@ reset:
 save_boot_params_ret:
 
 #if CONFIG_POSITION_INDEPENDENT
+	/* Verify that we're 4K aligned.  */
+	adr	x0, _start
+	ands	x0, x0, #0xfff
+	b.eq	1f
+0:
+	/*
+	 * FATAL, can't continue.
+	 * U-Boot needs to be loaded at a 4K aligned address.
+	 *
+	 * We use ADRP and ADD to load some symbol addresses during startup.
+	 * The ADD uses an absolute (non pc-relative) lo12 relocation
+	 * thus requiring 4K alignment.
+	 */
+	wfi
+	b	0b
+1:
+
 	/*
 	 * Fix .rela.dyn relocations. This allows U-Boot to be loaded to and
 	 * executed at a different address than it was linked at.
Signature · 1 line
2.25.1
#3 lore raw

PATCH v3 3/4 arm64: Add support for larger PIE U-Boot

In reply to Edgar E. Iglesias

From: "Edgar E. Iglesias" <[email protected]>

Linking a U-Boot larger than 1MB fails with PIE enabled:
u-boot/arch/arm/cpu/armv8/start.S:71:(.text+0x3c): relocation truncated to fit: R_AARCH64_ADR_PREL_LO21 against symbol `__rel_dyn_end' defined in .bss_start section in u-boot.

This extends the supported range by using adrp & add to load symbols early while starting up.

---
 arch/arm/cpu/armv8/start.S | 6 ++++--
 arch/arm/lib/crt0_64.S     | 8 +++++++-
 2 files changed, 11 insertions(+), 3 deletions(-)
arch/arm/cpu/armv8/start.S +4 -2
index 85baebc5f7..e5c2856cf5 100644
@@ -84,8 +84,10 @@ pie_fixup:
 	adr	x0, _start		/* x0 <- Runtime value of _start */
 	ldr	x1, _TEXT_BASE		/* x1 <- Linked value of _start */
 	sub	x9, x0, x1		/* x9 <- Run-vs-link offset */
-	adr	x2, __rel_dyn_start	/* x2 <- Runtime &__rel_dyn_start */
-	adr	x3, __rel_dyn_end	/* x3 <- Runtime &__rel_dyn_end */
+	adrp    x2, __rel_dyn_start     /* x2 <- Runtime &__rel_dyn_start */
+	add     x2, x2, #:lo12:__rel_dyn_start
+	adrp    x3, __rel_dyn_end       /* x3 <- Runtime &__rel_dyn_end */
+	add     x3, x3, #:lo12:__rel_dyn_end
 pie_fix_loop:
 	ldp	x0, x1, [x2], #16	/* (x0, x1) <- (Link location, fixup) */
 	ldr	x4, [x2], #8		/* x4 <- addend */
arch/arm/lib/crt0_64.S +7 -1
index 04afa518ac..9d2319c0e8 100644
@@ -73,7 +73,12 @@ ENTRY(_main)
 #elif defined(CONFIG_SPL_BUILD) && defined(CONFIG_SPL_STACK)
 	ldr	x0, =(CONFIG_SPL_STACK)
 #elif defined(CONFIG_INIT_SP_RELATIVE)
+#if CONFIG_POSITION_INDEPENDENT
+	adrp	x0, __bss_start     /* x0 <- Runtime &__bss_start */
+	add	x0, x0, #:lo12:__bss_start
+#else
 	adr	x0, __bss_start
+#endif
 	add	x0, x0, #CONFIG_SYS_INIT_SP_BSS_OFFSET
 #else
 	ldr	x0, =(CONFIG_SYS_INIT_SP_ADDR)
@@ -102,7 +107,8 @@ ENTRY(_main)
 	adr	lr, relocation_return
 #if CONFIG_POSITION_INDEPENDENT
 	/* Add in link-vs-runtime offset */
-	adr	x0, _start		/* x0 <- Runtime value of _start */
+	adrp	x0, _start		/* x0 <- Runtime value of _start */
+	add	x0, x0, #:lo12:_start
 	ldr	x9, _TEXT_BASE		/* x9 <- Linked value of _start */
 	sub	x9, x9, x0		/* x9 <- Run-vs-link offset */
 	add	lr, lr, x9
Signature · 1 line
2.25.1
#4 lore raw

PATCH v3 3/4 arm64: Add support for larger PIE U-Boot

Quoted 52 lines · Edgar E. Iglesias

From: "Edgar E. Iglesias" <[email protected]>

Linking a U-Boot larger than 1MB fails with PIE enabled:
u-boot/arch/arm/cpu/armv8/start.S:71:(.text+0x3c): relocation truncated to fit: R_AARCH64_ADR_PREL_LO21 against symbol `__rel_dyn_end' defined in .bss_start section in u-boot.

This extends the supported range by using adrp & add to load symbols early while starting up.

---
 arch/arm/cpu/armv8/start.S | 6 ++++--
 arch/arm/lib/crt0_64.S     | 8 +++++++-
 2 files changed, 11 insertions(+), 3 deletions(-)
arch/arm/cpu/armv8/start.S +4 -2
index 85baebc5f7..e5c2856cf5 100644
@@ -84,8 +84,10 @@ pie_fixup:
 	adr	x0, _start		/* x0 <- Runtime value of _start */
 	ldr	x1, _TEXT_BASE		/* x1 <- Linked value of _start */
 	sub	x9, x0, x1		/* x9 <- Run-vs-link offset */
-	adr	x2, __rel_dyn_start	/* x2 <- Runtime &__rel_dyn_start */
-	adr	x3, __rel_dyn_end	/* x3 <- Runtime &__rel_dyn_end */
+	adrp    x2, __rel_dyn_start     /* x2 <- Runtime &__rel_dyn_start */
+	add     x2, x2, #:lo12:__rel_dyn_start
+	adrp    x3, __rel_dyn_end       /* x3 <- Runtime &__rel_dyn_end */
+	add     x3, x3, #:lo12:__rel_dyn_end
 pie_fix_loop:
 	ldp	x0, x1, [x2], #16	/* (x0, x1) <- (Link location, fixup) */
 	ldr	x4, [x2], #8		/* x4 <- addend */
arch/arm/lib/crt0_64.S +5 -0
index 04afa518ac..9d2319c0e8 100644
@@ -73,7 +73,12 @@ ENTRY(_main)
 #elif defined(CONFIG_SPL_BUILD) && defined(CONFIG_SPL_STACK)
 	ldr	x0, =(CONFIG_SPL_STACK)
 #elif defined(CONFIG_INIT_SP_RELATIVE)
+#if CONFIG_POSITION_INDEPENDENT
+	adrp	x0, __bss_start     /* x0 <- Runtime &__bss_start */
+	add	x0, x0, #:lo12:__bss_start
+#else
 	adr	x0, __bss_start
+#endif
 	add	x0, x0, #CONFIG_SYS_INIT_SP_BSS_OFFSET
 #else
 	ldr	x0, =(CONFIG_SYS_INIT_SP_ADDR)

arch/arm/lib/crt0_64.S ENTRY(_main) · line 114

Quoted 9 lines
arch/arm/lib/crt0_64.S +2 -1
@@ -102,7 +107,8 @@ ENTRY(_main)
 	adr	lr, relocation_return
 #if CONFIG_POSITION_INDEPENDENT
 	/* Add in link-vs-runtime offset */
-	adr	x0, _start		/* x0 <- Runtime value of _start */
+	adrp	x0, _start		/* x0 <- Runtime value of _start */
+	add	x0, x0, #:lo12:_start
 	ldr	x9, _TEXT_BASE		/* x9 <- Linked value of _start */
 	sub	x9, x9, x0		/* x9 <- Run-vs-link offset */
 	add	lr, lr, x9

Thanks,
Michal

#5 lore raw

PATCH v3 4/4 arm64: Trap non-PIE builds early if starting from wrong address

In reply to Edgar E. Iglesias

From: "Edgar E. Iglesias" <[email protected]>

Trap non-PIE builds early if the start address doesn't match between run-time and link-time. This will trap the startup sequence rather than letting it run into obscure errors.

---
 arch/arm/cpu/armv8/start.S | 13 +++++++++++++
 1 file changed, 13 insertions(+)
arch/arm/cpu/armv8/start.S +13 -0
index e5c2856cf5..39e1b842c4 100644
@@ -101,6 +101,19 @@ pie_skip_reloc:
 	cmp	x2, x3
 	b.lo	pie_fix_loop
 pie_fixup_done:
+#else
+	adr	x0, _start
+	ldr	x1, _TEXT_BASE
+	cmp	x0, x1
+	beq	1f
+0:
+	/*
+	 * FATAL, can't continue.
+	 * U-Boot needs to start executing at CONFIG_SYS_TEXT_BASE.
+	 */
+	wfi
+	b	0b
+1:
 #endif
 
 #ifdef CONFIG_SYS_RESET_SCTRL
Signature · 1 line
2.25.1
#6 lore raw

PATCH v3 4/4 arm64: Trap non-PIE builds early if starting from wrong address

Quoted 26 lines · Edgar E. Iglesias

From: "Edgar E. Iglesias" <[email protected]>

Trap non-PIE builds early if the start address doesn't match between run-time and link-time. This will trap the startup sequence rather than letting it run into obscure errors.

---
 arch/arm/cpu/armv8/start.S | 13 +++++++++++++
 1 file changed, 13 insertions(+)
arch/arm/cpu/armv8/start.S +6 -0
index e5c2856cf5..39e1b842c4 100644
@@ -101,6 +101,19 @@ pie_skip_reloc:
 	cmp	x2, x3
 	b.lo	pie_fix_loop
 pie_fixup_done:
+#else
+	adr	x0, _start
+	ldr	x1, _TEXT_BASE
+	cmp	x0, x1
+	beq	1f
+0:

arch/arm/cpu/armv8/start.S pie_skip_reloc: · line 119

Quoted 10 lines
arch/arm/cpu/armv8/start.S +7 -0
+	/*
+	 * FATAL, can't continue.
+	 * U-Boot needs to start executing at CONFIG_SYS_TEXT_BASE.
+	 */
+	wfi
+	b	0b
+1:
 #endif
 
 #ifdef CONFIG_SYS_RESET_SCTRL

NACK for this.

1. It breaks SPL flow because CONFIG_SYS_TEXT_BASE is text base for U-Boot proper
2. It likely also breaks TPL flow for the same reason

3. And last thing is that this code is used only for U-Boot proper.
.globl _TEXT_BASE
_TEXT_BASE:
.quad CONFIG_SYS_TEXT_BASE

The fixes are below. Point 3 should be likely be in separate patch because it is unrelated.

Thanks,
Michal

arch/arm/cpu/armv8/start.S +4 -1
index b37dbabf4d42..cdc609e873fc 100644
@@ -33,10 +33,11 @@ _start:
 
        .align 3
 
+#if !(defined(CONFIG_SPL_BUILD) || defined(CONFIG_TPL_BUILD))
 .globl _TEXT_BASE
 _TEXT_BASE:
        .quad   CONFIG_SYS_TEXT_BASE
-
+#endif
 /*
  * These are defined in the linker script.
  */
@@ -102,6 +103,7 @@ pie_skip_reloc:
        b.lo    pie_fix_loop
 pie_fixup_done:
 #else
+#if !(defined(CONFIG_SPL_BUILD) || defined(CONFIG_TPL_BUILD))
        adr     x0, _start
        ldr     x1, _TEXT_BASE
        cmp     x0, x1
@@ -115,6 +117,7 @@ pie_fixup_done:
        b       0b
 1:
 #endif
+#endif
 
 #ifdef CONFIG_SYS_RESET_SCTRL
        bl reset_sctrl
#7 lore raw

PATCH v3 4/4 arm64: Trap non-PIE builds early if starting from wrong address

Quoted 46 lines · Michal Simek
Quoted 26 lines · Edgar E. Iglesias

From: "Edgar E. Iglesias" <[email protected]>

Trap non-PIE builds early if the start address doesn't match between run-time and link-time. This will trap the startup sequence rather than letting it run into obscure errors.

---
 arch/arm/cpu/armv8/start.S | 13 +++++++++++++
 1 file changed, 13 insertions(+)
arch/arm/cpu/armv8/start.S +6 -0
index e5c2856cf5..39e1b842c4 100644
@@ -101,6 +101,19 @@ pie_skip_reloc:
 	cmp	x2, x3
 	b.lo	pie_fix_loop
 pie_fixup_done:
+#else
+	adr	x0, _start
+	ldr	x1, _TEXT_BASE
+	cmp	x0, x1
+	beq	1f
+0:

arch/arm/cpu/armv8/start.S pie_skip_reloc: · line 119

Quoted 10 lines
arch/arm/cpu/armv8/start.S +7 -0
+	/*
+	 * FATAL, can't continue.
+	 * U-Boot needs to start executing at CONFIG_SYS_TEXT_BASE.
+	 */
+	wfi
+	b	0b
+1:
 #endif
 
 #ifdef CONFIG_SYS_RESET_SCTRL

NACK for this.

1. It breaks SPL flow because CONFIG_SYS_TEXT_BASE is text base for U-Boot proper
2. It likely also breaks TPL flow for the same reason

Quoted 7 lines

3. And last thing is that this code is used only for U-Boot proper.
.globl _TEXT_BASE
_TEXT_BASE:
.quad CONFIG_SYS_TEXT_BASE

The fixes are below. Point 3 should be likely be in separate patch because it is unrelated.

So if this patch causes issues, can't we just drop it? I mean right now you will probably just crash anyway if you load it at the wrong address, but maybe late enough that you get more hints or even some output.

Now this patch makes sure that you don't get anything, so I don't see how this is really improving the situation. It seems like a case of "don't fix things that ain't broken".

Cheers,
Andre

Quoted 39 lines

Thanks,
Michal

arch/arm/cpu/armv8/start.S +4 -1
index b37dbabf4d42..cdc609e873fc 100644
@@ -33,10 +33,11 @@ _start:
 
        .align 3
 
+#if !(defined(CONFIG_SPL_BUILD) || defined(CONFIG_TPL_BUILD))
 .globl _TEXT_BASE
 _TEXT_BASE:
        .quad   CONFIG_SYS_TEXT_BASE
-
+#endif
 /*
  * These are defined in the linker script.
  */
@@ -102,6 +103,7 @@ pie_skip_reloc:
        b.lo    pie_fix_loop
 pie_fixup_done:
 #else
+#if !(defined(CONFIG_SPL_BUILD) || defined(CONFIG_TPL_BUILD))
        adr     x0, _start
        ldr     x1, _TEXT_BASE
        cmp     x0, x1
@@ -115,6 +117,7 @@ pie_fixup_done:
        b       0b
 1:
 #endif
+#endif
 
 #ifdef CONFIG_SYS_RESET_SCTRL
        bl reset_sctrl
#8 lore raw

PATCH v3 4/4 arm64: Trap non-PIE builds early if starting from wrong address

Quoted 55 lines · Andr? Przywara
Quoted 46 lines · Michal Simek
Quoted 26 lines · Edgar E. Iglesias

From: "Edgar E. Iglesias" <[email protected]>

Trap non-PIE builds early if the start address doesn't match between run-time and link-time. This will trap the startup sequence rather than letting it run into obscure errors.

---
 arch/arm/cpu/armv8/start.S | 13 +++++++++++++
 1 file changed, 13 insertions(+)
arch/arm/cpu/armv8/start.S +6 -0
index e5c2856cf5..39e1b842c4 100644
@@ -101,6 +101,19 @@ pie_skip_reloc:
 	cmp	x2, x3
 	b.lo	pie_fix_loop
 pie_fixup_done:
+#else
+	adr	x0, _start
+	ldr	x1, _TEXT_BASE
+	cmp	x0, x1
+	beq	1f
+0:

arch/arm/cpu/armv8/start.S pie_skip_reloc: · line 119

Quoted 10 lines
arch/arm/cpu/armv8/start.S +7 -0
+	/*
+	 * FATAL, can't continue.
+	 * U-Boot needs to start executing at CONFIG_SYS_TEXT_BASE.
+	 */
+	wfi
+	b	0b
+1:
 #endif
 
 #ifdef CONFIG_SYS_RESET_SCTRL

NACK for this.

1. It breaks SPL flow because CONFIG_SYS_TEXT_BASE is text base for U-Boot proper
2. It likely also breaks TPL flow for the same reason

Quoted 7 lines

3. And last thing is that this code is used only for U-Boot proper.
.globl _TEXT_BASE
_TEXT_BASE:
.quad CONFIG_SYS_TEXT_BASE

The fixes are below. Point 3 should be likely be in separate patch because it is unrelated.

Quoted 7 lines

So if this patch causes issues, can't we just drop it? I mean right now you will probably just crash anyway if you load it at the wrong address, but maybe late enough that you get more hints or even some output.

Now this patch makes sure that you don't get anything, so I don't see how this is really improving the situation. It seems like a case of "don't fix things that ain't broken".

I am fine with dropping it.
Tom: What do you think?

Thanks,
Michal

#9 lore raw

PATCH v3 4/4 arm64: Trap non-PIE builds early if starting from wrong address

Quoted 62 lines · Michal Simek
Quoted 59 lines · Andr? Przywara
Quoted 46 lines · Michal Simek
Quoted 26 lines · Edgar E. Iglesias

From: "Edgar E. Iglesias" <[email protected]>

Trap non-PIE builds early if the start address doesn't match between run-time and link-time. This will trap the startup sequence rather than letting it run into obscure errors.

---
 arch/arm/cpu/armv8/start.S | 13 +++++++++++++
 1 file changed, 13 insertions(+)
arch/arm/cpu/armv8/start.S +6 -0
index e5c2856cf5..39e1b842c4 100644
@@ -101,6 +101,19 @@ pie_skip_reloc:
 	cmp	x2, x3
 	b.lo	pie_fix_loop
 pie_fixup_done:
+#else
+	adr	x0, _start
+	ldr	x1, _TEXT_BASE
+	cmp	x0, x1
+	beq	1f
+0:

arch/arm/cpu/armv8/start.S pie_skip_reloc: · line 119

Quoted 10 lines
arch/arm/cpu/armv8/start.S +7 -0
+	/*
+	 * FATAL, can't continue.
+	 * U-Boot needs to start executing at CONFIG_SYS_TEXT_BASE.
+	 */
+	wfi
+	b	0b
+1:
 #endif
 
 #ifdef CONFIG_SYS_RESET_SCTRL

NACK for this.

1. It breaks SPL flow because CONFIG_SYS_TEXT_BASE is text base for U-Boot proper
2. It likely also breaks TPL flow for the same reason

Quoted 7 lines

3. And last thing is that this code is used only for U-Boot proper.
.globl _TEXT_BASE
_TEXT_BASE:
.quad CONFIG_SYS_TEXT_BASE

The fixes are below. Point 3 should be likely be in separate patch because it is unrelated.

So if this patch causes issues, can't we just drop it? I mean right now you will probably just crash anyway if you load it at the wrong address, but maybe late enough that you get more hints or even some output.

Quoted 6 lines
Quoted 3 lines

Now this patch makes sure that you don't get anything, so I don't see how this is really improving the situation. It seems like a case of "don't fix things that ain't broken".

I am fine with dropping it.
Tom: What do you think?

OK, yes, we can set this aside for now at least. I assume this is all for v2021.01 anyhow?

Signature · 8 lines
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 659 bytes
Desc: not available
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20200910/f310e4ad/attachment.sig>
#10 lore raw

PATCH v3 4/4 arm64: Trap non-PIE builds early if starting from wrong address

Quoted 50 lines · Tom Rini
Quoted 49 lines · Michal Simek
Quoted 46 lines · Andr? Przywara
Quoted 33 lines · Michal Simek
Quoted 21 lines · Edgar E. Iglesias

From: "Edgar E. Iglesias" <[email protected]>

Trap non-PIE builds early if the start address doesn't match between run-time and link-time. This will trap the startup sequence rather than letting it run into obscure errors.

Signed-off-by: Edgar E. Iglesias <[email protected]> --- arch/arm/cpu/armv8/start.S | 13 +++++++++++++ 1 file changed, 13 insertions(+)

(quoted diff) +0 -0

b/arch/arm/cpu/armv8/start.S index e5c2856cf5..39e1b842c4 100644 --- a/arch/arm/cpu/armv8/start.S +++ b/arch/arm/cpu/armv8/start.S @@ -101,6 +101,19 @@
pie_skip_reloc: cmp x2, x3 b.lo pie_fix_loop
pie_fixup_done: +#else + adr x0, _start + ldr x1,
_TEXT_BASE + cmp x0, x1 + beq 1f +0: + /* + * FATAL, can't
continue. + * U-Boot needs to start executing at
CONFIG_SYS_TEXT_BASE. + */ + wfi + b 0b +1: #endif

Quoted 2 lines

#ifdef CONFIG_SYS_RESET_SCTRL

NACK for this.

1. It breaks SPL flow because CONFIG_SYS_TEXT_BASE is text base for U-Boot proper 2. It likely also breaks TPL flow for the same reason

Quoted 6 lines

3. And last thing is that this code is used only for U-Boot
proper. .globl _TEXT_BASE _TEXT_BASE: .quad
CONFIG_SYS_TEXT_BASE

The fixes are below. Point 3 should be likely be in separate patch because it is unrelated.

So if this patch causes issues, can't we just drop it? I mean right now you will probably just crash anyway if you load it at the wrong address, but maybe late enough that you get more hints or even some output.

Quoted 9 lines
Quoted 5 lines
Quoted 3 lines

Now this patch makes sure that you don't get anything, so I don't see how this is really improving the situation. It seems like a case of "don't fix things that ain't broken".

I am fine with dropping it. Tom: What do you think?

OK, yes, we can set this aside for now at least. I assume this is all for v2021.01 anyhow?

I would target it for 2021.01.

Thanks,
Michal

#11 lore raw

PATCH v3 4/4 arm64: Trap non-PIE builds early if starting from wrong address

Quoted 57 lines · Michal Simek
Quoted 54 lines · Tom Rini
Quoted 53 lines · Michal Simek
Quoted 49 lines · Andr? Przywara
Quoted 33 lines · Michal Simek
Quoted 21 lines · Edgar E. Iglesias

From: "Edgar E. Iglesias" <[email protected]>

Trap non-PIE builds early if the start address doesn't match between run-time and link-time. This will trap the startup sequence rather than letting it run into obscure errors.

Signed-off-by: Edgar E. Iglesias <[email protected]> --- arch/arm/cpu/armv8/start.S | 13 +++++++++++++ 1 file changed, 13 insertions(+)

(quoted diff) +0 -0

b/arch/arm/cpu/armv8/start.S index e5c2856cf5..39e1b842c4 100644 --- a/arch/arm/cpu/armv8/start.S +++ b/arch/arm/cpu/armv8/start.S @@ -101,6 +101,19 @@
pie_skip_reloc: cmp x2, x3 b.lo pie_fix_loop
pie_fixup_done: +#else + adr x0, _start + ldr x1,
_TEXT_BASE + cmp x0, x1 + beq 1f +0: + /* + * FATAL, can't
continue. + * U-Boot needs to start executing at
CONFIG_SYS_TEXT_BASE. + */ + wfi + b 0b +1: #endif

Quoted 2 lines

#ifdef CONFIG_SYS_RESET_SCTRL

NACK for this.

1. It breaks SPL flow because CONFIG_SYS_TEXT_BASE is text base for U-Boot proper 2. It likely also breaks TPL flow for the same reason

Quoted 6 lines

3. And last thing is that this code is used only for U-Boot
proper. .globl _TEXT_BASE _TEXT_BASE: .quad
CONFIG_SYS_TEXT_BASE

The fixes are below. Point 3 should be likely be in separate patch because it is unrelated.

So if this patch causes issues, can't we just drop it? I mean right now you will probably just crash anyway if you load it at the wrong address, but maybe late enough that you get more hints or even some output.

Now this patch makes sure that you don't get anything, so I don't see how this is really improving the situation. It seems like a case of "don't fix things that ain't broken".

Quoted 8 lines
Quoted 5 lines
Quoted 1 line

I am fine with dropping it. Tom: What do you think?

OK, yes, we can set this aside for now at least. I assume this is all for v2021.01 anyhow?

I would target it for 2021.01.

Dropping #4 and queueing the rest for 2021.01 sounds good to me too. We can revisit a possible check for non-PIE later.

Cheers,
Edgar

#12 lore raw

v3 cover arm64: Large PIE fixes

In reply to Edgar E. Iglesias
Quoted 9 lines · Edgar E. Iglesias

From: "Edgar E. Iglesias" <[email protected]>

This fixes some build issues with large (> 1MB) PIE U-Boot setups. We also document the 4K aligned load address requirement and add an early run-time check for it.

As requested by reviewers, I've also added a runtime check for non-PIE builds to trap the startup sequence early if the start address doesn't match between run-time and link-time.

The series,

#13 lore raw

v3 cover arm64: Large PIE fixes

In reply to Edgar E. Iglesias

Hi,

Quoted 35 lines · Edgar E. Iglesias

From: "Edgar E. Iglesias" <[email protected]>

This fixes some build issues with large (> 1MB) PIE U-Boot setups. We also document the 4K aligned load address requirement and add an early run-time check for it.

As requested by reviewers, I've also added a runtime check for non-PIE builds to trap the startup sequence early if the start address doesn't match between run-time and link-time.

Cheers,
Edgar

ChangeLog:
v2 -> v3:
* Add non-PIE start address (run vs link-time) check
* Move 4K aligment Kconfig help description
* Fix load of __bss_start
* Use x0 rather than x1 in PIE load-address check
* Add missing tabs
* Add load-address check for non-PIE
* U-boot -> U-Boot in a few places
* Tweak commit messages

v1 -> v2:
* Fix adr of _start in arch/arm/lib/crt0_64.S
* Add early check and bail out into a WFI loop when not 4K aligned
* Document the 4K alignement requirement in Kconfig

Edgar E. Iglesias (4):
arm64: Mention 4K aligned load addresses in the PIE Kconfig help
arm64: Trap PIE builds early if load address is not 4K aligned
arm64: Add support for larger PIE U-Boot
arm64: Trap non-PIE builds early if starting from wrong address

Quoted 5 lines
 arch/arm/Kconfig           |  4 ++--
 arch/arm/cpu/armv8/start.S | 36 ++++++++++++++++++++++++++++++++++--
 arch/arm/lib/crt0_64.S     |  8 +++++++-
 3 files changed, 43 insertions(+), 5 deletions(-)

Because these changes are made for supporting Xilinx SOCs 1-3 applied to my tree. Patch 4 is dropped as was agreed.

Thanks,
Michal

Signature · 5 lines
Michal Simek, Ing. (M.Eng), OpenPGP -> KeyID: FE3D1F91
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel - Xilinx Microblaze
Maintainer of Linux kernel - Xilinx Zynq ARM and ZynqMP ARM64 SoCs
U-Boot custodian - Xilinx Microblaze/Zynq/ZynqMP/Versal SoCs