Received-SPF: pass (google.com: domain of linux-kernel+bounces-204499-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.80.249 as permitted sender) client-ip=147.75.80.249;
Date: Thu, 6 Jun 2024 17:37:49 +0300
From: Mike Rapoport <rppt@kernel.org>
To: Borislav Petkov <bp@kernel.org>, Jan Beulich <jbeulich@suse.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	"Borislav Petkov (AMD)" <bp@alien8.de>,
	Narasimhan V <Narasimhan.V@amd.com>
Subject: Re: [PATCH] x86/mm/numa: Use NUMA_NO_NODE when calling
 memblock_set_node()
Message-ID: <ZmHJvY5h887hDN87@kernel.org>
References: <20240603141005.23261-1-bp@kernel.org>
 <171750701353.925406.16431237983148253122.b4-ty@kernel.org>
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <171750701353.925406.16431237983148253122.b4-ty@kernel.org>

On Tue, Jun 04, 2024 at 04:16:57PM +0300, Mike Rapoport wrote:
> On Mon, 03 Jun 2024 16:10:05 +0200, Borislav Petkov wrote:
> > memblock_set_node() warns about using MAX_NUMNODES, see
> > 
> >   e0eec24e2e19 ("memblock: make memblock_set_node() also warn about use of MAX_NUMNODES")
> > 
> > for details.
> > 
> > 
> > [...]
> 
> Applied to fixes branch of memblock.git tree, thanks!
> 
> [1/1] x86/mm/numa: Use NUMA_NO_NODE when calling memblock_set_node()
>       commit: c55f3cc2d9f241d6e45336fd48dafa755c012297
> 
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/rppt/memblock
> branch: fixes

There was a similar, but better fix from Jan Beulich:

https://lore.kernel.org/lkml/abadb736-a239-49e4-ab42-ace7acdd4278@suse.com/

that also updated numa_clear_kernel_node_hotplug().

I'm going to replace this patch with his and use Boris' changelog as more
appropriate.
 
> --
> Sincerely yours,
> Mike.
> 

-- 
Sincerely yours,
Mike.