linux-kernel - Re: [PATCH] mm/sparse: Fix sparse_vmemmap_init_nid_early definition without CONFIG

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <3cdc6bd6-f0c4-410f-b2a2-8cc2b5d1c522@kernel.org>
Date: Thu, 27 Nov 2025 10:46:54 +0100
From: "David Hildenbrand (Red Hat)" <david@...nel.org>
To: Jinhui Guo <guojinhui.liam@...edance.com>, akpm@...ux-foundation.org,
 lorenzo.stoakes@...cle.com, Liam.Howlett@...cle.com, vbabka@...e.cz,
 rppt@...nel.org, surenb@...gle.com, mhocko@...e.com, fvdl@...gle.com
Cc: linux-mm@...ck.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] mm/sparse: Fix sparse_vmemmap_init_nid_early definition
 without CONFIG_SPARSEMEM

On 11/27/25 10:25, Jinhui Guo wrote:
> When CONFIG_SPARSEMEM is disabled, the macro
> sparse_vmemmap_init_nid_early(_nid, _use) passes
> two arguments, while the actual function accepts
> only nid. Drop the extra argument _use.
> 
> Fixes: d65917c42373 ("mm/sparse: allow for alternate vmemmap section init at boot")
> Signed-off-by: Jinhui Guo <guojinhui.liam@...edance.com>
> ---
>   include/linux/mmzone.h | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/include/linux/mmzone.h b/include/linux/mmzone.h
> index 7fb7331c5725..f6dd181a4821 100644
> --- a/include/linux/mmzone.h
> +++ b/include/linux/mmzone.h
> @@ -2293,7 +2293,7 @@ void sparse_init(void);
>   #else
>   #define sparse_init()	do {} while (0)
>   #define sparse_index_init(_sec, _nid)  do {} while (0)
> -#define sparse_vmemmap_init_nid_early(_nid, _use) do {} while (0)
> +#define sparse_vmemmap_init_nid_early(_nid) do {} while (0)
>   #define sparse_vmemmap_init_nid_late(_nid) do {} while (0)
>   #define pfn_in_present_section pfn_valid
>   #define subsection_map_init(_pfn, _nr_pages) do {} while (0)

That commit is from early 2025.

So what are the symptoms we are fixing? I would have assumed a 
compile-time problem, but no built bot caught that?

-- 
Cheers

David