From: Sascha Hauer <s.hauer@pengutronix.de>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>,
BAREBOX <barebox@lists.infradead.org>,
Sascha Hauer <s.hauer@pengutronix.de>
Subject: Re: [PATCH v3 0/6] ARM: Map sections RO/XN
Date: Mon, 23 Jun 2025 13:55:07 +0200 [thread overview]
Message-ID: <175067970714.2975289.16397944775348185929.b4-ty@pengutronix.de> (raw)
In-Reply-To: <20250618-mmu-xn-ro-v3-0-2a9825725934@pengutronix.de>
On Wed, 18 Jun 2025 11:34:46 +0200, Sascha Hauer wrote:
> So far we mapped all RAM as read write with execute permission. This
> series series hardens this a bit. The barebox text segment will be
> mapped readonly with execute permission, the RO data section as readonly
> without execute permission and the remaining RAM will lose its execute
> permission.
>
> I tested this series on ARMv5, ARMv7 and ARMv8. I am not confident
> though that there are no regressions, so this new behaviour is behind a
> Kconfig option. It is default-y, but can be disabled for debugging
> purposses. Once this series has proven stable it can be removed.
>
> [...]
Applied, thanks!
[1/6] ARM: pass barebox base to mmu_early_enable()
https://git.pengutronix.de/cgit/barebox/commit/?id=6762fbcbf8a1 (link may not be stable)
[2/6] ARM: mmu: move ARCH_MAP_WRITECOMBINE to header
https://git.pengutronix.de/cgit/barebox/commit/?id=51d012fd31e2 (link may not be stable)
[3/6] ARM: MMU: map memory for barebox proper pagewise
https://git.pengutronix.de/cgit/barebox/commit/?id=930e19bfdd2e (link may not be stable)
[4/6] ARM: MMU: map text segment ro and data segments execute never
https://git.pengutronix.de/cgit/barebox/commit/?id=5916385fae83 (link may not be stable)
[5/6] ARM: MMU64: map memory for barebox proper pagewise
https://git.pengutronix.de/cgit/barebox/commit/?id=59c1288698b4 (link may not be stable)
[6/6] ARM: MMU64: map text segment ro and data segments execute never
https://git.pengutronix.de/cgit/barebox/commit/?id=03dfb3f142fb (link may not be stable)
Best regards,
--
Sascha Hauer <s.hauer@pengutronix.de>
prev parent reply other threads:[~2025-06-23 13:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-18 9:34 Sascha Hauer
2025-06-18 9:34 ` [PATCH v3 1/6] ARM: pass barebox base to mmu_early_enable() Sascha Hauer
2025-06-18 9:34 ` [PATCH v3 2/6] ARM: mmu: move ARCH_MAP_WRITECOMBINE to header Sascha Hauer
2025-06-18 9:34 ` [PATCH v3 3/6] ARM: MMU: map memory for barebox proper pagewise Sascha Hauer
2025-06-18 9:34 ` [PATCH v3 4/6] ARM: MMU: map text segment ro and data segments execute never Sascha Hauer
2025-06-18 9:34 ` [PATCH v3 5/6] ARM: MMU64: map memory for barebox proper pagewise Sascha Hauer
2025-06-18 9:34 ` [PATCH v3 6/6] ARM: MMU64: map text segment ro and data segments execute never Sascha Hauer
2025-06-23 11:55 ` 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=175067970714.2975289.16397944775348185929.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