From: <nobuhiro1.iwamatsu@toshiba.co.jp>
To: <rppt@kernel.org>
Cc: <linux-mm@kvack.org>, <akpm@linux-foundation.org>,
<linux-kernel@vger.kernel.org>, <yuji2.ishikawa@toshiba.co.jp>
Subject: RE: [PATCH RFC] mm: numa_clear_kernel_node_hotplug: Add NUMA_NO_NODE check for node id
Date: Wed, 16 Oct 2024 08:58:05 +0000 [thread overview]
Message-ID: <OS0PR01MB63886680F6999A56E19558F892462@OS0PR01MB6388.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <Zw91Ynr53eGwj91r@kernel.org>
Hi Mike,
> -----Original Message-----
> From: Mike Rapoport <rppt@kernel.org>
> Sent: Wednesday, October 16, 2024 5:12 PM
> To: iwamatsu nobuhiro(岩松 信洋 ○DITC□DIT○OST)
> <nobuhiro1.iwamatsu@toshiba.co.jp>
> Cc: linux-mm@kvack.org; Andrew Morton <akpm@linux-foundation.org>;
> linux-kernel@vger.kernel.org; ishikawa yuji(石川 悠司 ○RDC□AITC○
> EA開) <yuji2.ishikawa@toshiba.co.jp>
> Subject: Re: [PATCH RFC] mm: numa_clear_kernel_node_hotplug: Add
> NUMA_NO_NODE check for node id
>
> On Wed, Oct 16, 2024 at 02:37:10PM +0900, Nobuhiro Iwamatsu wrote:
> > The acquired memory blocks for reserved may include blocks outside of
> > memory management. In this case, the nid variable is set to
> > NUMA_NO_NODE (-1), so an error occurs in node_set().
> > This adds a check to numa_clear_kernel_node_hotplug that skips
> > node_set when nid is set to NUMA_NO_NODE.
> >
> > Fixes: 87482708210f ("mm: introduce numa_memblks")
> > Suggested-by: Yuji Ishikawa <yuji2.ishikawa@toshiba.co.jp>
> > Signed-off-by: Nobuhiro Iwamatsu <nobuhiro1.iwamatsu@toshiba.co.jp>
> > Cc: Mike Rapoport (Microsoft) <rppt@kernel.org>
> > ---
> > mm/numa_memblks.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/mm/numa_memblks.c b/mm/numa_memblks.c index
> > be52b93a9c58..b982f9260872 100644
> > --- a/mm/numa_memblks.c
> > +++ b/mm/numa_memblks.c
> > @@ -349,7 +349,7 @@ static void __init
> numa_clear_kernel_node_hotplug(void)
> > for_each_reserved_mem_region(mb_region) {
> > int nid = memblock_get_region_node(mb_region);
> >
> > - if (nid != MAX_NUMNODES)
> > + if (nid != NUMA_NO_NODE && nid != MAX_NUMNODES)
>
> We have numa_valid_node() check for this, please use that.
Thanks. I will send v2 with it.
> Otherwise
>
> Reviewed-by: Mike Rapoport (Microsoft) <rppt@kernel.org>
>
> > node_set(nid, reserved_nodemask);
> > }
> >
> > --
> > 2.45.2
> >
> >
>
> --
> Sincerely yours,
> Mike.
Best regards,
Nobuhiro
prev parent reply other threads:[~2024-10-16 8:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-16 5:37 Nobuhiro Iwamatsu
2024-10-16 8:12 ` Mike Rapoport
2024-10-16 8:58 ` nobuhiro1.iwamatsu [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=OS0PR01MB63886680F6999A56E19558F892462@OS0PR01MB6388.jpnprd01.prod.outlook.com \
--to=nobuhiro1.iwamatsu@toshiba.co.jp \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rppt@kernel.org \
--cc=yuji2.ishikawa@toshiba.co.jp \
/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