From: Ahmad Fatoum <a.fatoum@barebox.org>
To: barebox@lists.infradead.org
Subject: [PATCH master 0/8] ARM: mmu: fix hang reserving memory after text area
Date: Tue, 5 Aug 2025 19:45:33 +0200 [thread overview]
Message-ID: <20250805174541.2606267-1-a.fatoum@barebox.org> (raw)
The loop remapping the memory banks looks at reserved memory
regions and then maps everything eXecute Never up to the start of the
region. If the region happens to be in the same bank as the text area
and it comes after it, this means the text area is temporarily mapped
eXecute Never, while barebox is running from it, which results in a
hang.
Fix this by remapping only after both reserved memory regions and text
area have been considered.
This series is a rebase of
https://lore.barebox.org/barebox/aJHagEVHUpHjALa2@pengutronix.de/T/#t
Ahmad Fatoum (8):
partition: rename region_overlap_end to region_overlap_end_inclusive
partition: define new region_overlap_end_exclusive helper
ARM: mmu: skip TLB invalidation if remapping zero bytes
ARM64: mmu: pass map type not PTE flags to early_remap_range
ARM: mmu: provide setup_trap_pages for both 32- and 64-bit
ARM: mmu: setup trap pages before remapping R/O
ARM: mmu: share common memory bank remapping code
ARM: mmu: fix hang reserving memory after text area
arch/arm/cpu/mmu-common.c | 69 +++++++++++++++++++++++++++++++++++++++
arch/arm/cpu/mmu-common.h | 1 +
arch/arm/cpu/mmu_32.c | 44 ++-----------------------
arch/arm/cpu/mmu_64.c | 51 +++++++----------------------
commands/iomemport.c | 2 +-
common/partitions.c | 6 ++--
include/range.h | 30 ++++++++++++++---
7 files changed, 114 insertions(+), 89 deletions(-)
--
2.39.5
next reply other threads:[~2025-08-05 18:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-05 17:45 Ahmad Fatoum [this message]
2025-08-05 17:45 ` [PATCH master 1/8] partition: rename region_overlap_end to region_overlap_end_inclusive Ahmad Fatoum
2025-08-05 17:45 ` [PATCH master 2/8] partition: define new region_overlap_end_exclusive helper Ahmad Fatoum
2025-08-05 17:45 ` [PATCH master 3/8] ARM: mmu: skip TLB invalidation if remapping zero bytes Ahmad Fatoum
2025-08-05 17:45 ` [PATCH master 4/8] ARM64: mmu: pass map type not PTE flags to early_remap_range Ahmad Fatoum
2025-08-05 17:45 ` [PATCH master 5/8] ARM: mmu: provide setup_trap_pages for both 32- and 64-bit Ahmad Fatoum
2025-08-05 17:45 ` [PATCH master 6/8] ARM: mmu: setup trap pages before remapping R/O Ahmad Fatoum
2025-08-05 17:45 ` [PATCH master 7/8] ARM: mmu: share common memory bank remapping code Ahmad Fatoum
2025-08-05 17:45 ` [PATCH master 8/8] ARM: mmu: fix hang reserving memory after text area Ahmad Fatoum
2025-08-06 6:31 ` [PATCH master 0/8] " Sascha Hauer
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=20250805174541.2606267-1-a.fatoum@barebox.org \
--to=a.fatoum@barebox.org \
--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