From: Mike Rapoport <rppt@kernel.org>
To: Muchun Song <muchun.song@linux.dev>
Cc: Muchun Song <songmuchun@bytedance.com>,
Madhavan Srinivasan <maddy@linux.ibm.com>,
Andrew Morton <akpm@linux-foundation.org>,
David Hildenbrand <david@kernel.org>,
Michael Ellerman <mpe@ellerman.id.au>,
Nicholas Piggin <npiggin@gmail.com>,
Christophe Leroy <chleroy@kernel.org>,
Ritesh Harjani <ritesh.list@gmail.com>,
Shrikanth Hegde <sshegde@linux.ibm.com>,
Lorenzo Stoakes <ljs@kernel.org>,
"Liam R . Howlett" <liam@infradead.org>,
Vlastimil Babka <vbabka@kernel.org>,
Suren Baghdasaryan <surenb@google.com>,
Michal Hocko <mhocko@suse.com>, Qi Zheng <qi.zheng@linux.dev>,
Lance Yang <lance.yang@linux.dev>,
linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: [PATCH v4 6/6] mm/mm_init: add zone mismatch warning during page init
Date: Sat, 10 Oct 2026 11:58:15 +0200 [thread overview]
Message-ID: <asoMN5F-3qvaW5w0@kernel.org> (raw)
In-Reply-To: <434B0573-BF18-4413-9BDF-C5873CC13206@linux.dev>
On Sat, Oct 10, 2026 at 05:32:59PM +0800, Muchun Song wrote:
>
>
> > On Oct 10, 2026, at 15:57, Muchun Song <songmuchun@bytedance.com> wrote:
> >
> > For vmemmap-optimized sections, tail struct pages may be backed by
> > shared vmemmap pages. Those shared pages must carry the same page zone
> > ID as the struct pages initialized for the section.
> >
> > Warn in __init_single_page() if the shared tail page has a different
> > page_zone_id(), which would indicate inconsistent initialization.
>
> Please ignore Sashiko's report [1], both are false positive. It didn't
> realize that shared vmemmap pages are initialized early before __init_single_page().
I didn't realize it too when I read this first :)
How about a short comment above vmemmap_optimization_verify_zone()?
> [1] https://sashiko.dev/#/patchset/20261010075755.83339-1-songmuchun%40bytedance.com?part=6
>
> Thanks.
--
Sincerely yours,
Mike.
next prev parent reply other threads:[~2026-10-10 9:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-10 7:57 [PATCH v4 0/6] mm: Unify device DAX and HugeTLB vmemmap population paths Muchun Song
2026-10-10 7:57 ` [PATCH v4 1/6] mm/sparse-vmemmap: drop VMEMMAP_POPULATE_DAX Muchun Song
2026-10-10 7:57 ` [PATCH v4 2/6] mm/sparse-vmemmap: support device DAX in common vmemmap path Muchun Song
2026-10-10 7:57 ` [PATCH v4 3/6] mm/sparse-vmemmap: drop Device DAX-specific population path Muchun Song
2026-10-10 8:37 ` Muchun Song
2026-10-10 7:57 ` [PATCH v4 4/6] mm/sparse-vmemmap: remove the unused ptpfn argument Muchun Song
2026-10-10 7:57 ` [PATCH v4 5/6] mm/sparse-vmemmap: open-code vmemmap_populate_address() Muchun Song
2026-10-10 7:57 ` [PATCH v4 6/6] mm/mm_init: add zone mismatch warning during page init Muchun Song
2026-10-10 9:32 ` Muchun Song
2026-10-10 9:58 ` Mike Rapoport [this message]
2026-10-10 10:33 ` Muchun Song
2026-10-10 11:55 ` [PATCH] fixup! " Muchun Song
2026-10-10 20:42 ` [PATCH v4 0/6] mm: Unify device DAX and HugeTLB vmemmap population paths Andrew Morton
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=asoMN5F-3qvaW5w0@kernel.org \
--to=rppt@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=chleroy@kernel.org \
--cc=david@kernel.org \
--cc=lance.yang@linux.dev \
--cc=liam@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=ljs@kernel.org \
--cc=maddy@linux.ibm.com \
--cc=mhocko@suse.com \
--cc=mpe@ellerman.id.au \
--cc=muchun.song@linux.dev \
--cc=npiggin@gmail.com \
--cc=qi.zheng@linux.dev \
--cc=ritesh.list@gmail.com \
--cc=songmuchun@bytedance.com \
--cc=sshegde@linux.ibm.com \
--cc=surenb@google.com \
--cc=vbabka@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.