All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Rapoport <rppt@kernel.org>
To: Wandun Chen <chenwandun1@gmail.com>
Cc: robh@kernel.org, saravanak@kernel.org, m.szyprowski@samsung.com,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org, akpm@linux-foundation.org
Subject: Re: [PATCH v3 0/5] of: reserved_mem: several fixes about reserved memory
Date: Tue, 22 Sep 2026 11:48:41 +0300	[thread overview]
Message-ID: <arJA6fOMetzoBhDH@kernel.org> (raw)
In-Reply-To: <20260920092852.614973-1-chenwandun1@gmail.com>

On Sun, Sep 20, 2026 at 05:28:47PM +0800, Wandun Chen wrote:
> From: Wandun Chen <chenwandun@lixiang.com>
> 
> This series fixes several error-handling issues in the reserved-memory
> initialization paths.
> 
> The first two patches fix cleanup of no-map regions after driver
> initialization failure.
> 
> Static reserved-memory nodes are reserved during the early DT scan but
> initialized later. The third patch tags regions whose early reservation
> succeeded, so the late scan can skip the nodes whose early reservation
> failed.
> 
> The last two patches reject overlapping static regions. Without
> these checks, overlapping nodes can be initialized over the same
> physical memory, result in data corrupt.
> 
> Sashiko reported these issues in [1] [2] [3].
> 
> [1] https://sashiko.dev/#/message/20260814090305.4C8741F00A3D%40smtp.kernel.org
> [2] https://sashiko.dev/#/message/20260814084718.29C341F000E9%40smtp.kernel.org
> [3] https://sashiko.dev/#/message/20260806100605.2C2C01F000E9%40smtp.kernel.org
> 
> v2 --> v3:
> 1. Rework the mechanism that checks in the late scan whether the early
>    reservation succeeded (patches 3-5, suggested by Marek, thanks).
> 
>    Patch 3 adds a new memblock flag MEMBLOCK_RSRV_RMEM, which is set when
>    the early reservation of a static region succeeds and checked in the
>    late scan.

Can we keep this local to of_reserved_mem please?
 
>    Patches 4 and 5 are reworked to reject regions that overlap or are
>    contained by an existing reservation. The code makes a little different
>    from what was acked in v2, so the Acked-by tags for these patches are not
>    carried over.
> 
> 2. Reorder the patches: the two cleanup fixes in v2 now come first.
>    In v3, the first patch now introduces the 'dynamic' distinction in
>    fdt_init_reserved_mem_node(), which the following patche 3 build on,
>    so the series reads more fluently.
> 
> v1 --> v2:
> 1. Rework failed-node tracking in patch 1: do not track zero-sized nodes,
>    and keep a reserved_mem slot when tracking overflows.
> 2. Reject static reserved regions overlapping existing no-map regions.
> 3. Keep MEMBLOCK_NOMAP flag for static no-map regions when init failure.
> 
> 
> Wandun Chen (5):
>   of: reserved_mem: release dynamically allocated no-map region on init
>     failure
>   of: reserved_mem: retain static no-map memory on init failure
>   of: reserved_mem: skip init for regions whose early reservation failed
>   of: reserved_mem: reject static regions overlapping no-map memory
>   of: reserved_mem: reject static mapped regions overlapping existing
>     reservations
> 
>  drivers/of/of_reserved_mem.c | 86 +++++++++++++++++++++++++-------
>  include/linux/memblock.h     |  7 +++
>  mm/memblock.c                | 95 ++++++++++++++++++++++++++++++++++++
>  3 files changed, 170 insertions(+), 18 deletions(-)
> 
> -- 
> 2.43.0
> 

-- 
Sincerely yours,
Mike.

  parent reply	other threads:[~2026-09-22  8:48 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-20  9:28 [PATCH v3 0/5] of: reserved_mem: several fixes about reserved memory Wandun Chen
2026-09-20  9:28 ` [PATCH v3 1/5] of: reserved_mem: release dynamically allocated no-map region on init failure Wandun Chen
2026-09-20  9:28 ` [PATCH v3 2/5] of: reserved_mem: retain static no-map memory " Wandun Chen
2026-09-20  9:28 ` [PATCH v3 3/5] of: reserved_mem: skip init for regions whose early reservation failed Wandun Chen
2026-09-20  9:28 ` [PATCH v3 4/5] of: reserved_mem: reject static regions overlapping no-map memory Wandun Chen
2026-09-20 10:03   ` sashiko-bot
2026-09-20  9:28 ` [PATCH v3 5/5] of: reserved_mem: reject static mapped regions overlapping existing reservations Wandun Chen
2026-09-20 10:13   ` sashiko-bot
2026-09-22  8:48 ` Mike Rapoport [this message]
2026-09-22  9:24   ` [PATCH v3 0/5] of: reserved_mem: several fixes about reserved memory Wandun
2026-10-03  8:04     ` Mike Rapoport
2026-10-06 13:26       ` Marek Szyprowski
2026-10-08  6:38         ` Mike Rapoport
2026-10-08  9:43           ` Marek Szyprowski

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=arJA6fOMetzoBhDH@kernel.org \
    --to=rppt@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=chenwandun1@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=m.szyprowski@samsung.com \
    --cc=robh@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.