From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: barebox@lists.infradead.org
Cc: Ahmad Fatoum <a.fatoum@pengutronix.de>
Subject: [PATCH 1/2] hardening: make stack guard page the default
Date: Wed, 9 Jul 2025 12:18:47 +0200 [thread overview]
Message-ID: <20250709101848.4039929-1-a.fatoum@pengutronix.de> (raw)
We have had guard page support for close to two years now and it's time
we start enabling it by default to catch stack overflows.
Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
---
lib/Kconfig.hardening | 1 +
1 file changed, 1 insertion(+)
diff --git a/lib/Kconfig.hardening b/lib/Kconfig.hardening
index 658de4953aa1..53bf4d5bb956 100644
--- a/lib/Kconfig.hardening
+++ b/lib/Kconfig.hardening
@@ -153,6 +153,7 @@ config FORTIFY_SOURCE
config STACK_GUARD_PAGE
bool "Place guard page to catch stack overflows"
depends on ARM && MMU
+ default y
help
When enabled, barebox places a faulting guard page to catch total
stack usage exceeding CONFIG_STACK_SIZE. On overflows, that hit
--
2.39.5
next reply other threads:[~2025-07-09 12:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-09 10:18 Ahmad Fatoum [this message]
2025-07-09 10:18 ` [PATCH 2/2] hardening: update text after addition of CONFIG_ARM_MMU_PERMISSIONS Ahmad Fatoum
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=20250709101848.4039929-1-a.fatoum@pengutronix.de \
--to=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