From: "David Hildenbrand (Arm)" <david@kernel.org>
To: Muchun Song <songmuchun@bytedance.com>,
Andrew Morton <akpm@linux-foundation.org>,
Muchun Song <muchun.song@linux.dev>,
Oscar Salvador <osalvador@suse.de>,
Michael Ellerman <mpe@ellerman.id.au>,
Madhavan Srinivasan <maddy@linux.ibm.com>
Cc: Lorenzo Stoakes <ljs@kernel.org>,
"Liam R . Howlett" <Liam.Howlett@oracle.com>,
Vlastimil Babka <vbabka@kernel.org>,
Mike Rapoport <rppt@kernel.org>,
Suren Baghdasaryan <surenb@google.com>,
Michal Hocko <mhocko@suse.com>,
Nicholas Piggin <npiggin@gmail.com>,
Christophe Leroy <chleroy@kernel.org>,
aneesh.kumar@linux.ibm.com, joao.m.martins@oracle.com,
linux-mm@kvack.org, linuxppc-dev@lists.ozlabs.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v6 7/7] mm/memory_hotplug: Factor out altmap freeing checks
Date: Fri, 24 Apr 2026 09:34:43 +0200 [thread overview]
Message-ID: <6dd8e62b-97e3-4261-92c7-ba3a02ae6397@kernel.org> (raw)
In-Reply-To: <20260424025547.3806072-8-songmuchun@bytedance.com>
On 4/24/26 04:55, Muchun Song wrote:
> Use a small helper to centralize altmap freeing after verifying that all
> vmemmap pages were released. This keeps the check consistent between the
> normal teardown path and the memory hotplug error paths.
>
> Suggested-by: David Hildenbrand (Arm) <david@kernel.org>
> Signed-off-by: Muchun Song <songmuchun@bytedance.com>
> ---
Thanks!
Acked-by: David Hildenbrand (Arm) <david@kernel.org>
Andrew usually prefers sending non-fixes separately, but he can tell us how he
prefers it in this case here.
--
Cheers,
David
next prev parent reply other threads:[~2026-04-24 7:34 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-24 2:55 [PATCH v6 0/7] mm: fix vmemmap optimization accounting and initialization Muchun Song
2026-04-24 2:55 ` [PATCH v6 1/7] mm/sparse-vmemmap: Fix vmemmap accounting underflow Muchun Song
2026-04-24 2:55 ` [PATCH v6 2/7] mm/memory_hotplug: Fix incorrect altmap passing in error path Muchun Song
2026-04-24 2:55 ` [PATCH v6 3/7] mm/sparse-vmemmap: Pass @pgmap argument to memory deactivation paths Muchun Song
2026-04-24 2:55 ` [PATCH v6 4/7] mm/sparse-vmemmap: Fix DAX vmemmap accounting with optimization Muchun Song
2026-04-24 7:33 ` David Hildenbrand (Arm)
2026-04-24 7:48 ` Muchun Song
2026-04-25 3:05 ` Muchun Song
2026-04-25 5:48 ` David Hildenbrand (Arm)
2026-04-25 6:20 ` Muchun Song
2026-04-25 6:47 ` David Hildenbrand (Arm)
2026-04-25 6:56 ` Muchun Song
2026-04-24 2:55 ` [PATCH v6 5/7] mm/mm_init: Fix pageblock migratetype for ZONE_DEVICE compound pages Muchun Song
2026-04-24 2:55 ` [PATCH v6 6/7] mm/mm_init: Fix uninitialized struct pages for ZONE_DEVICE Muchun Song
2026-04-24 8:20 ` Mike Rapoport
2026-04-24 2:55 ` [PATCH v6 7/7] mm/memory_hotplug: Factor out altmap freeing checks Muchun Song
2026-04-24 7:34 ` David Hildenbrand (Arm) [this message]
2026-04-24 10:20 ` Andrew Morton
2026-04-24 11:58 ` Muchun Song
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=6dd8e62b-97e3-4261-92c7-ba3a02ae6397@kernel.org \
--to=david@kernel.org \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.ibm.com \
--cc=chleroy@kernel.org \
--cc=joao.m.martins@oracle.com \
--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=osalvador@suse.de \
--cc=rppt@kernel.org \
--cc=songmuchun@bytedance.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox