From: Anshuman Khandual <anshuman.khandual@arm.com>
To: Li Zhijian <lizhijian@fujitsu.com>, linux-mm@kvack.org
Cc: David Hildenbrand <david@redhat.com>,
Oscar Salvador <osalvador@suse.de>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm/memory_hotplug: Print the correct pfn in do_migrate_range()
Date: Tue, 24 Sep 2024 16:20:13 +0530 [thread overview]
Message-ID: <42545fc6-8c91-4f20-9959-2416b9e112c2@arm.com> (raw)
In-Reply-To: <20240924101555.327091-1-lizhijian@fujitsu.com>
On 9/24/24 15:45, Li Zhijian wrote:
> The pfn value needs to be retrieved correctly when PageTransHuge(page)
Where the pfn could have been modified with
pfn = page_to_pfn(head) + compound_nr(head) - 1
So retrieving from page will get the original pfn value ?
> is true. Fix it by replacing the usage of 'pfn' with 'page_to_pfn(page)'
> to ensure the correct pfn is printed in warning messages when isolation
> fails.
>
> Signed-off-by: Li Zhijian <lizhijian@fujitsu.com>
> ---
> mm/memory_hotplug.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/mm/memory_hotplug.c b/mm/memory_hotplug.c
> index 26790c8d5b43..000430406a9e 100644
> --- a/mm/memory_hotplug.c
> +++ b/mm/memory_hotplug.c
> @@ -1829,7 +1829,7 @@ static void do_migrate_range(unsigned long start_pfn, unsigned long end_pfn)
>
> } else {
> if (__ratelimit(&migrate_rs)) {
> - pr_warn("failed to isolate pfn %lx\n", pfn);
> + pr_warn("failed to isolate pfn %lx\n", page_to_pfn(page));
> dump_page(page, "isolation failed");
> }
> }
next prev parent reply other threads:[~2024-09-24 10:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-24 10:15 Li Zhijian
2024-09-24 10:50 ` Anshuman Khandual [this message]
2024-09-25 8:01 ` Zhijian Li (Fujitsu)
2024-09-25 8:59 ` Zhijian Li (Fujitsu)
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=42545fc6-8c91-4f20-9959-2416b9e112c2@arm.com \
--to=anshuman.khandual@arm.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lizhijian@fujitsu.com \
--cc=osalvador@suse.de \
/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