Devicetree
 help / color / mirror / Atom feed
From: Paul Walmsley <pjw@kernel.org>
To: Marek Szyprowski <m.szyprowski@samsung.com>
Cc: linux-riscv@lists.infradead.org, devicetree@vger.kernel.org,
	 linux-mm@kvack.org, Paul Walmsley <pjw@kernel.org>,
	 Palmer Dabbelt <palmer@dabbelt.com>,
	Albert Ou <aou@eecs.berkeley.edu>,
	 Alexandre Ghiti <alex@ghiti.fr>,
	Conor Dooley <conor.dooley@microchip.com>,
	 Geert Uytterhoeven <geert@linux-m68k.org>,
	Rob Herring <robh@kernel.org>,  Mike Rapoport <rppt@kernel.org>,
	Saravana Kannan <saravanak@kernel.org>,
	 Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] riscv: mm: reserve the DTB before scanning reserved memory
Date: Tue, 17 Nov 2026 20:35:42 -0700 (MST)	[thread overview]
Message-ID: <3e5a01c1-1d91-8bc0-0589-0621930c2d18@kernel.org> (raw)
In-Reply-To: <20261104104604.3370384-1-m.szyprowski@samsung.com>

On Wed, 4 Nov 2026, Marek Szyprowski wrote:

> early_init_fdt_scan_reserved_mem() allocates memory from memblock while
> it scans /reserved-memory: the reserved_mem array, and the regions that
> are placed dynamically by size. On RISC-V the DTB was only reserved
> after that scan, so memblock could hand out the memory the DTB occupies
> while the DTB was still being parsed.
> 
> Reserve the DTB before the scan, so that memblock never allocates from
> it.
> 
> Fixes: ef69d2559fe9 ("riscv: Move early dtb mapping into the fixmap region")
> Closes: https://lore.kernel.org/all/b71ac175-fba5-4f61-bbdb-0b98dec9ccee@samsung.com/
> Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>

Thanks, queued for v7.4-rc with a stable@ cc.


- Paul

      reply	other threads:[~2026-11-18  3:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20261104104615eucas1p2583cd5bc9ae36bd9ff2d28f87d6e7583@eucas1p2.samsung.com>
2026-11-04 10:46 ` [PATCH] riscv: mm: reserve the DTB before scanning reserved memory Marek Szyprowski
2026-11-18  3:35   ` Paul Walmsley [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=3e5a01c1-1d91-8bc0-0589-0621930c2d18@kernel.org \
    --to=pjw@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=alex@ghiti.fr \
    --cc=aou@eecs.berkeley.edu \
    --cc=conor.dooley@microchip.com \
    --cc=devicetree@vger.kernel.org \
    --cc=geert@linux-m68k.org \
    --cc=linux-mm@kvack.org \
    --cc=linux-riscv@lists.infradead.org \
    --cc=m.szyprowski@samsung.com \
    --cc=palmer@dabbelt.com \
    --cc=robh@kernel.org \
    --cc=rppt@kernel.org \
    --cc=saravanak@kernel.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