From: Mike Rapoport <rppt@kernel.org>
To: akpm@linux-foundation.org, yajun.deng@linux.dev,
Wei Yang <richard.weiyang@gmail.com>
Cc: Mike Rapoport <rppt@kernel.org>, linux-mm@kvack.org
Subject: Re: [Patch v2 0/3] memblock: some fix for memmap_init_reserved_pages()
Date: Mon, 7 Apr 2025 09:34:06 +0300 [thread overview]
Message-ID: <174400754464.63656.4237088728418234476.b4-ty@kernel.org> (raw)
In-Reply-To: <20250318071948.23854-1-richard.weiyang@gmail.com>
On Tue, 18 Mar 2025 07:19:45 +0000, Wei Yang wrote:
> During code review, I found we may leave some reserved region with invalid nid
> when memblock_set_node() double the array. The patch set propose a fix and
> test case.
>
> Also I found memblock_set_node() accept size instead of end as second
> parameter. Currently it is misused.
>
> [...]
Applied to for-next branch of memblock.git tree, thanks!
[1/3] mm/memblock: pass size instead of end to memblock_set_node()
commit: 06eaa824fd239edd1eab2754f29b2d03da313003
[2/3] mm/memblock: repeat setting reserved region nid if array is doubled
commit: eac8ea8736ccc09513152d970eb2a42ed78e87e8
[3/3] memblock tests: add test for memblock_set_node
commit: 3b394dff15e14550a26b133fc7b556b5b526f6a5
tree: https://git.kernel.org/pub/scm/linux/kernel/git/rppt/memblock
branch: for-next
--
Sincerely yours,
Mike.
prev parent reply other threads:[~2025-04-07 6:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-18 7:19 Wei Yang
2025-03-18 7:19 ` [Patch v2 1/3] mm/memblock: pass size instead of end to memblock_set_node() Wei Yang
2025-03-18 10:29 ` Anshuman Khandual
2025-03-18 7:19 ` [Patch v2 2/3] mm/memblock: repeat setting reserved region nid if array is doubled Wei Yang
2025-03-18 10:55 ` Anshuman Khandual
2025-03-19 8:12 ` Wei Yang
2025-03-18 7:19 ` [Patch v2 3/3] memblock tests: add test for memblock_set_node Wei Yang
2025-04-07 2:58 ` [Patch v2 0/3] memblock: some fix for memmap_init_reserved_pages() Wei Yang
2025-04-07 6:34 ` Mike Rapoport [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=174400754464.63656.4237088728418234476.b4-ty@kernel.org \
--to=rppt@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=richard.weiyang@gmail.com \
--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