From: Sascha Hauer <s.hauer@pengutronix.de>
To: barebox@lists.infradead.org, Ahmad Fatoum <a.fatoum@pengutronix.de>
Subject: Re: [PATCH master 1/4] KASan: fix possible breakage with CONFIG_INIT_STACK_ALL
Date: Tue, 22 Apr 2025 11:29:51 +0200 [thread overview]
Message-ID: <174531419157.3015406.7996489393130071492.b4-ty@pengutronix.de> (raw)
In-Reply-To: <20250422075519.219029-1-a.fatoum@pengutronix.de>
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.hauer@pengutronix.de>
prev parent reply other threads:[~2025-04-22 10:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-22 7:55 Ahmad Fatoum
2025-04-22 7:55 ` [PATCH master 2/4] ARM: Layerscape: fix compilation of LS1028 without LS1046 Ahmad Fatoum
2025-04-22 14:14 ` Sascha Hauer
2025-04-22 14:18 ` Ahmad Fatoum
2025-04-22 7:55 ` [PATCH master 3/4] ARM: k3: define debug_ll_write_reg only on CONFIG_DEBUG_AM62X_UART=y Ahmad Fatoum
2025-04-22 14:23 ` Sascha Hauer
2025-04-22 14:29 ` Ahmad Fatoum
2025-04-22 14:34 ` Sascha Hauer
2025-04-22 7:55 ` [PATCH master 4/4] memory: correct return value in request_barebox_region stub Ahmad Fatoum
2025-04-22 9:29 ` Sascha Hauer [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-all 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=174531419157.3015406.7996489393130071492.b4-ty@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
/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