From 7395398ad273f11569f4c4f3fb45219b916480eb Mon Sep 17 00:00:00 2001 From: Alexey Brodkin Date: Mon, 20 Jan 2014 14:30:39 +0400 Subject: [PATCH] board_r - fixup functions table after relocation This is only required for "PIC" relocation and doesn't apply to modern "PIE" relocation which does data relocation as well as code. "init_sequence_r" is just an array that consists of compile-time adresses of init functions. Since this is basically an array of integers (pointers to "void" to be more precise) it won't be modified during relocation - it will be just copied to new location as it is. As a consequence on execution after relocation "initcall_run_list" will be jumping to pre-relocation addresses. As long as we don't overwrite pre-relocation memory area init calls are executed correctly. But still it is dangerous because after relocation we don't expect initially used memory to stay untouched. Cc: Tom Rini Cc: Masahiro Yamada Cc: Doug Anderson Cc: Thomas Langer Cc: Albert ARIBAUD Acked-by: Simon Glass Signed-off-by: Alexey Brodkin --- common/board_r.c | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/common/board_r.c b/common/board_r.c index 86ca1cbbd4..c2d0763b57 100644 --- a/common/board_r.c +++ b/common/board_r.c @@ -903,9 +903,19 @@ init_fnc_t init_sequence_r[] = { void board_init_r(gd_t *new_gd, ulong dest_addr) { +#ifdef CONFIG_NEEDS_MANUAL_RELOC + int i; +#endif + #ifndef CONFIG_X86 gd = new_gd; #endif + +#ifdef CONFIG_NEEDS_MANUAL_RELOC + for (i = 0; i < ARRAY_SIZE(init_sequence_r); i++) + init_sequence_r[i] += gd->reloc_off; +#endif + if (initcall_run_list(init_sequence_r)) hang(); -- 2.25.1