mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: barebox@lists.infradead.org, Ahmad Fatoum <a.fatoum@barebox.org>
Subject: Re: [PATCH master 0/8] ARM: mmu: fix hang reserving memory after text area
Date: Wed, 06 Aug 2025 08:31:16 +0200	[thread overview]
Message-ID: <175446187621.1954232.5137409844451448531.b4-ty@pengutronix.de> (raw)
In-Reply-To: <20250805174541.2606267-1-a.fatoum@barebox.org>


On Tue, 05 Aug 2025 19:45:33 +0200, Ahmad Fatoum wrote:
> 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.
> 
> [...]

Applied, thanks!

[1/8] partition: rename region_overlap_end to region_overlap_end_inclusive
      https://git.pengutronix.de/cgit/barebox/commit/?id=f6c2846933ca (link may not be stable)
[2/8] partition: define new region_overlap_end_exclusive helper
      https://git.pengutronix.de/cgit/barebox/commit/?id=768fdb36f30e (link may not be stable)
[3/8] ARM: mmu: skip TLB invalidation if remapping zero bytes
      https://git.pengutronix.de/cgit/barebox/commit/?id=b71103970c9b (link may not be stable)
[4/8] ARM64: mmu: pass map type not PTE flags to early_remap_range
      https://git.pengutronix.de/cgit/barebox/commit/?id=fda2cc61ef68 (link may not be stable)
[5/8] ARM: mmu: provide setup_trap_pages for both 32- and 64-bit
      https://git.pengutronix.de/cgit/barebox/commit/?id=5a4f19a47c21 (link may not be stable)
[6/8] ARM: mmu: setup trap pages before remapping R/O
      https://git.pengutronix.de/cgit/barebox/commit/?id=b661f0519424 (link may not be stable)
[7/8] ARM: mmu: share common memory bank remapping code
      https://git.pengutronix.de/cgit/barebox/commit/?id=5c4d167f5a54 (link may not be stable)
[8/8] ARM: mmu: fix hang reserving memory after text area
      https://git.pengutronix.de/cgit/barebox/commit/?id=e91c073f4756 (link may not be stable)

Best regards,
-- 
Sascha Hauer <s.hauer@pengutronix.de>




      parent reply	other threads:[~2025-08-06  6:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-05 17:45 Ahmad Fatoum
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 ` 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=175446187621.1954232.5137409844451448531.b4-ty@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=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