mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: barebox@lists.infradead.org
Cc: Ahmad Fatoum <a.fatoum@pengutronix.de>
Subject: [PATCH master] Documentation: migration-2025.08.0: add note about W^X
Date: Fri, 24 Oct 2025 12:33:12 +0200	[thread overview]
Message-ID: <20251024103313.499868-1-a.fatoum@pengutronix.de> (raw)

CONFIG_ARM_MMU_PERMISSIONS was a relatively invasive change, so it
should be pointed out specifically to avoid users running into issues
with it.

Signed-off-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
---
 .../migration-guides/migration-2025.08.0.rst         | 12 ++++++++++++
 1 file changed, 12 insertions(+)

diff --git a/Documentation/migration-guides/migration-2025.08.0.rst b/Documentation/migration-guides/migration-2025.08.0.rst
index b40119ac672b..86412f25c36e 100644
--- a/Documentation/migration-guides/migration-2025.08.0.rst
+++ b/Documentation/migration-guides/migration-2025.08.0.rst
@@ -1,6 +1,18 @@
 Release v2025.08.0
 ==================
 
+W^X on ARM
+----------
+
+``CONFIG_ARM_MMU_PERMISSIONS=y`` is now the default and instructs barebox to map
+its memory regions with more restricted permissions: Data is no longer executable
+and code as well as read-only data is no longer writable.
+
+This can lead to breakage in code that had invalid assumptions beforehand,
+e.g. code expecting on-chip SRAMs to be executable or bogus code casting away
+const. Please report to upstream any issues that are resolved by disabling
+``CONFIG_ARM_MMU_PERMISSIONS``, so they can be properly fixed.
+
 Bootchooser
 -----------
 
-- 
2.47.3




                 reply	other threads:[~2025-10-24 10:33 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20251024103313.499868-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