On Tue, 22 Apr 2025 09:55:16 +0200, Ahmad Fatoum wrote:
> With CONFIG_INIT_STACK_ALL_PATTERN or CONFIG_INIT_STACK_ALL_ZERO,
> the compiler emits calls to memset to initialize variables on the stack.
>
> With kasan enabled, this would end up calling KASAN memset, which can
> lead to access of global variables prior to relocation.
>
> Brace ourselves for this situation by sidestepping KASAN prior to
> relocation.
>
> [...]
Applied, thanks!
[1/4] KASan: fix possible breakage with CONFIG_INIT_STACK_ALL
https://git.pengutronix.de/cgit/barebox/commit/?id=68aba118f469 (link may
not be stable)
[2/4] ARM: Layerscape: fix compilation of LS1028 without LS1046
https://git.pengutronix.de/cgit/barebox/commit/?id=7458e41a4c98 (link may
not be stable)
[3/4] ARM: k3: define debug_ll_write_reg only on CONFIG_DEBUG_AM62X_UART=y
https://git.pengutronix.de/cgit/barebox/commit/?id=6b749354d11a (link may
not be stable)
[4/4] memory: correct return value in request_barebox_region stub
https://git.pengutronix.de/cgit/barebox/commit/?id=1d7b03c94e3c (link may
not be stable)
Best regards,
--
Sascha Hauer <s.ha...@pengutronix.de>
