From: Wei Yang <richard.weiyang@gmail.com>
To: Mike Rapoport <rppt@kernel.org>
Cc: Wei Yang <richard.weiyang@gmail.com>,
akpm@linux-foundation.org, linux-mm@kvack.org,
Yajun Deng <yajun.deng@linux.dev>,
stable@vger.kernel.org
Subject: Re: [PATCH 2/3] mm/memblock: repeat setting reserved region nid if array is doubled
Date: Tue, 18 Mar 2025 02:58:09 +0000 [thread overview]
Message-ID: <20250318025809.v2jpjbwy3yhc7cik@master> (raw)
In-Reply-To: <Z9bvE-6KsbIGRcTm@kernel.org>
On Sun, Mar 16, 2025 at 05:32:35PM +0200, Mike Rapoport wrote:
>On Fri, Mar 14, 2025 at 02:03:51AM +0000, Wei Yang wrote:
>> On Thu, Mar 13, 2025 at 05:07:59PM +0200, Mike Rapoport wrote:
>> >> Commit 61167ad5fecd ("mm: pass nid to reserve_bootmem_region()") introduce
>> >> a way to set nid to all reserved region.
>> >>
>> >> But there is a corner case it will leave some region with invalid nid.
>> >> When memblock_set_node() doubles the array of memblock.reserved, it may
>> >> lead to a new reserved region before current position. The new region
>> >> will be left with an invalid node id.
>> >>
>> >> Repeat the process when detecting it.
>> >>
>> >> Fixes: 61167ad5fecd ("mm: pass nid to reserve_bootmem_region()")
>> >> Signed-off-by: Wei Yang <richard.weiyang@gmail.com>
>> >> CC: Mike Rapoport <rppt@kernel.org>
>> >> CC: Yajun Deng <yajun.deng@linux.dev>
>> >> CC: <stable@vger.kernel.org>
>> >> ---
>> >> mm/memblock.c | 12 ++++++++++++
>> >> 1 file changed, 12 insertions(+)
>> >>
>> >> diff --git a/mm/memblock.c b/mm/memblock.c
>> >> index 85442f1b7f14..302dd7bc622d 100644
>> >> --- a/mm/memblock.c
>> >> +++ b/mm/memblock.c
>> >> @@ -2184,7 +2184,10 @@ static void __init memmap_init_reserved_pages(void)
>> >> * set nid on all reserved pages and also treat struct
>> >> * pages for the NOMAP regions as PageReserved
>> >> */
>> >> +repeat:
>> >> for_each_mem_region(region) {
>> >> + unsigned long max = memblock.reserved.max;
>> >> +
>> >> nid = memblock_get_region_node(region);
>> >> start = region->base;
>> >> end = start + region->size;
>> >> @@ -2193,6 +2196,15 @@ static void __init memmap_init_reserved_pages(void)
>> >> reserve_bootmem_region(start, end, nid);
>> >>
>> >> memblock_set_node(start, region->size, &memblock.reserved, nid);
>> >> +
>> >> + /*
>> >> + * 'max' is changed means memblock.reserved has been doubled
>> >> + * its array, which may result a new reserved region before
>> >> + * current 'start'. Now we should repeat the procedure to set
>> >> + * its node id.
>> >> + */
>> >> + if (max != memblock.reserved.max)
>> >> + goto repeat;
>> >
>> >This check can be moved outside the loop, can't it?
>> >
>>
>> We can. You mean something like this?
>
>Yes, something like this.
>
>> diff --git a/mm/memblock.c b/mm/memblock.c
>> index 85442f1b7f14..67fd1695cce4 100644
>> --- a/mm/memblock.c
>> +++ b/mm/memblock.c
>> @@ -2179,11 +2179,14 @@ static void __init memmap_init_reserved_pages(void)
>> struct memblock_region *region;
>> phys_addr_t start, end;
>> int nid;
>> + unsigned long max;
>
>maybe max_reserved?
Sure, will update it.
>>
>> /*
>> * set nid on all reserved pages and also treat struct
>> * pages for the NOMAP regions as PageReserved
>> */
>> +repeat:
>> + max = memblock.reserved.max;
>> for_each_mem_region(region) {
>> nid = memblock_get_region_node(region);
>> start = region->base;
>> @@ -2194,6 +2197,13 @@ static void __init memmap_init_reserved_pages(void)
>>
>> memblock_set_node(start, region->size, &memblock.reserved, nid);
>> }
>> + /*
>> + * 'max' is changed means memblock.reserved has been doubled its
>> + * array, which may result a new reserved region before current
>> + * 'start'. Now we should repeat the procedure to set its node id.
>> + */
>> + if (max != memblock.reserved.max)
>> + goto repeat;
>>
>> /*
>> * initialize struct pages for reserved regions that don't have
>> --
>> Wei Yang
>> Help you, Help me
>
>--
>Sincerely yours,
>Mike.
--
Wei Yang
Help you, Help me
next prev parent reply other threads:[~2025-03-18 2:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-12 13:07 [PATCH 0/3] memblock: some fix for memmap_init_reserved_pages() Wei Yang
2025-03-12 13:07 ` [PATCH 1/3] mm/memblock: pass size instead of end to memblock_set_node() Wei Yang
2025-03-12 13:07 ` [PATCH 2/3] mm/memblock: repeat setting reserved region nid if array is doubled Wei Yang
2025-03-13 15:07 ` Mike Rapoport
2025-03-14 2:03 ` Wei Yang
2025-03-16 15:32 ` Mike Rapoport
2025-03-18 2:58 ` Wei Yang [this message]
2025-03-12 13:07 ` [PATCH 3/3] memblock tests: add test for memblock_set_node Wei Yang
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=20250318025809.v2jpjbwy3yhc7cik@master \
--to=richard.weiyang@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=rppt@kernel.org \
--cc=stable@vger.kernel.org \
--cc=yajun.deng@linux.dev \
/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