[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20250425180539.2b780a8b3d0958fcc2e8a500@linux-foundation.org>
Date: Fri, 25 Apr 2025 18:05:39 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: "Bernardo C. Gutierrez Cantu" <bercantu@...zon.de>
Cc: <dwmw2@...radead.org>, <linux-kernel@...r.kernel.org>,
<linux-mm@...ck.org>, <lkp@...el.com>, <rppt@...nel.org>,
<yajun.deng@...ux.dev>
Subject: Re: [PATCH] mm: memblock: Fix arguments passed to
memblock_set_node()
On Fri, 25 Apr 2025 10:20:03 +0000 "Bernardo C. Gutierrez Cantu" <bercantu@...zon.de> wrote:
> memblock_set_node() receives a `base` and a `size` arguments, but we are
> passing the `start` and `end` of the memory regions when iterating over
> them in memmap_init_reserved_pages() to set their node ids.
>
> This results in the function setting the node ids for the reserved memory
> regions in `[base, base + base + size)` instead of `[base, base + size)`.
>
> Pass `start` and `size`, so that we iterate over the correct range.
>
> Fixes: 61167ad5fecd ("mm: pass nid to reserve_bootmem_region()")
>
> ...
>
> --- a/mm/memblock.c
> +++ b/mm/memblock.c
> @@ -2196,7 +2196,7 @@ static void __init memmap_init_reserved_pages(void)
> if (memblock_is_nomap(region))
> reserve_bootmem_region(start, end, nid);
>
> - memblock_set_node(start, end, &memblock.reserved, nid);
> + memblock_set_node(start, region->size, &memblock.reserved, nid);
> }
>
> /*
What were the runtime effects of this bug?
Powered by blists - more mailing lists