From: Wei Yang <richard.weiyang@gmail.com>
To: akpm@linux-foundation.org, vbabka@suse.cz, surenb@google.com,
mhocko@suse.com, jackmanb@google.com, hannes@cmpxchg.org,
ziy@nvidia.com, david@redhat.com, lorenzo.stoakes@oracle.com,
Liam.Howlett@oracle.com, rppt@kernel.org, iamjoonsoo.kim@lge.com
Cc: linux-mm@kvack.org, Wei Yang <richard.weiyang@gmail.com>
Subject: [PATCH 0/2] mm/compaction: some fix for the range passed to pageblock_pfn_to_page()
Date: Thu, 2 Oct 2025 03:31:38 +0000 [thread overview]
Message-ID: <20251002033140.24462-1-richard.weiyang@gmail.com> (raw)
During the code reading of isolate_migratepages_range(), first spot the range
passed to pageblock_pfn_to_page() is different from that to
isolate_migratepages_block().
This implies there is a chance that pageblock_pfn_to_page() thinks the range
is in the same zone, but isolate_migratepages_block() will isolate range in
two different zones. This is not what we expect.
Then I found pageblock_pfn_to_page() has an optimization if zone->contiguous,
this means even the range is across two different zones, it will think the
range is within the same zone.
So introduce two patches to fix it:
Patch 1: check the range belongs to the zone first
Patch 2: pass the correct range to pageblock_pfn_to_page()
Wei Yang (2):
mm/compaction: check the range to pageblock_pfn_to_page() is within
the zone first
mm/compaction: fix the range to pageblock_pfn_to_page()
mm/compaction.c | 37 ++++++++++++++-----------------------
mm/internal.h | 3 +++
2 files changed, 17 insertions(+), 23 deletions(-)
--
2.34.1
next reply other threads:[~2025-10-02 3:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-02 3:31 Wei Yang [this message]
2025-10-02 3:31 ` [PATCH 1/2] mm/compaction: check the range to pageblock_pfn_to_page() is within the zone first Wei Yang
2025-10-08 10:14 ` David Hildenbrand
2025-10-09 2:08 ` Wei Yang
2025-10-09 7:19 ` David Hildenbrand
2025-10-02 3:31 ` [PATCH 2/2] mm/compaction: fix the range to pageblock_pfn_to_page() Wei Yang
2025-10-08 10:17 ` David Hildenbrand
2025-10-08 11:16 ` Michal Hocko
2025-10-09 3:39 ` Wei Yang
2025-10-08 1:29 ` [PATCH 0/2] mm/compaction: some fix for the range passed " Andrew Morton
2025-10-08 2:32 ` Wei Yang
2025-10-08 7:52 ` Michal Hocko
2025-10-08 9:13 ` Wei Yang
2025-10-08 9:55 ` David Hildenbrand
2025-11-11 23:32 ` 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=20251002033140.24462-1-richard.weiyang@gmail.com \
--to=richard.weiyang@gmail.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=hannes@cmpxchg.org \
--cc=iamjoonsoo.kim@lge.com \
--cc=jackmanb@google.com \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=mhocko@suse.com \
--cc=rppt@kernel.org \
--cc=surenb@google.com \
--cc=vbabka@suse.cz \
--cc=ziy@nvidia.com \
/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