From: David Hildenbrand <david@redhat.com>
To: Matthew Wilcox <willy@infradead.org>,
Sidhartha Kumar <sidhartha.kumar@oracle.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
akpm@linux-foundation.org, osalvador@suse.de
Subject: Re: [PATCH 1/2] mm/memory_hotplug: remove head page reference in do_migrate_range
Date: Tue, 24 Jan 2023 11:17:43 +0100 [thread overview]
Message-ID: <cd51d200-b3c5-0f1c-bae0-ef9903051e7a@redhat.com> (raw)
In-Reply-To: <Y87wJ6ERhdujjo6P@casper.infradead.org>
On 23.01.23 21:37, Matthew Wilcox wrote:
> On Mon, Jan 23, 2023 at 12:23:46PM -0800, Sidhartha Kumar wrote:
>> @@ -1637,14 +1637,13 @@ do_migrate_range(unsigned long start_pfn, unsigned long end_pfn)
>> continue;
>> page = pfn_to_page(pfn);
>> folio = page_folio(page);
>> - head = &folio->page;
>>
>> - if (PageHuge(page)) {
>> - pfn = page_to_pfn(head) + compound_nr(head) - 1;
>> + if (folio_test_hugetlb(folio)) {
>> + pfn = folio_pfn(folio) + folio_nr_pages(folio) - 1;
>> isolate_hugetlb(folio, &source);
>> continue;
>> - } else if (PageTransHuge(page))
>> - pfn = page_to_pfn(head) + thp_nr_pages(page) - 1;
>> + } else if (folio_test_transhuge(folio))
>> + pfn = folio_pfn(folio) + thp_nr_pages(page) - 1;
>
> I'm pretty sure those two lines should be...
>
> } else if (folio_test_large(folio))
> pfn = folio_pfn(folio) + folio_nr_pages(folio) - 1;
>
> But, erm ... we're doing this before we have a refcount on the page,
> right? So this is unsafe because the page might change which folio
> it is in. And the folio we found earlier might become a tail page
> of a different folio. (As the comment below explains, HWPoison pages
> won't, so it's not unsafe for them).
>
> Also, thp_nr_pages(page) is going to return 1 for tail pages. So this
> is a noop, unless page is a head page.
>
> It's all a bit confusing, and being memory-hotplug, it's not well
> tested. More thought needed.
Ehm, it is fairly well tested ;)
As memory offlining keeps retrying, temporarily making wrong assumptions
about a folio is acceptable, as long as we don't run into BUGs.
It's certainly worth a big comment in a code, that this is all racy and
that page migration code will stabilize.
Now, we could temporarily take a reference, but ... common migration
code will try taking its own ref to stabilize the page and would be
confused about yet another ref (-> migration will fail).
So we have to be careful about grabbing references on these pages, and
how long we're going to hold them. Otherwise we'll break memory
offlining completely :)
--
Thanks,
David / dhildenb
prev parent reply other threads:[~2023-01-24 10:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-23 20:23 Sidhartha Kumar
2023-01-23 20:23 ` [PATCH 2/2] mm/memory_hotplug: remove head page reference in scan_movable_pages() Sidhartha Kumar
2023-01-23 20:39 ` Matthew Wilcox
2023-01-23 20:37 ` [PATCH 1/2] mm/memory_hotplug: remove head page reference in do_migrate_range Matthew Wilcox
2023-01-23 21:08 ` Sidhartha Kumar
2023-01-24 2:32 ` Matthew Wilcox
2023-01-24 10:17 ` David Hildenbrand [this message]
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=cd51d200-b3c5-0f1c-bae0-ef9903051e7a@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=osalvador@suse.de \
--cc=sidhartha.kumar@oracle.com \
--cc=willy@infradead.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