From: Dev Jain <dev.jain@arm.com>
To: "Lorenzo Stoakes (ARM)" <ljs@kernel.org>
Cc: akpm@linux-foundation.org, david@kernel.org,
muchun.song@linux.dev, osalvador@suse.de, riel@surriel.com,
liam@infradead.org, vbabka@kernel.org, harry@kernel.org,
jannh@google.com, lance.yang@linux.dev, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, ryan.roberts@arm.com,
anshuman.khandual@arm.com
Subject: Re: [PATCH v3 1/5] mm/rmap: convert page -> folio for hwpoison checks
Date: Sat, 25 Jul 2026 13:06:25 +0530 [thread overview]
Message-ID: <8d2f756a-12a2-43bb-8849-3e71c1ce5d8f@arm.com> (raw)
In-Reply-To: <amMtRejoVMX2IV2V@lucifer>
On 24/07/26 2:50 pm, Lorenzo Stoakes (ARM) wrote:
> On Mon, Jul 13, 2026 at 05:00:44AM +0000, Dev Jain wrote:
>> try_to_unmap() receives hugetlb folios only from the hwpoison path.
>> hugetlb_update_hwpoison() sets the hugetlb folio's head-page
>> hwpoison bit, and page_vma_mapped_walk() reports the hugetlb mapping at
>> the head PFN, so the previous PageHWPoison(subpage) check happened to
>> work for hugetlb.
>>
>> For non-hugetlb folios, unmap_poisoned_folio() currently rejects large
>> folios before calling try_to_unmap(). Hence it is always the case that
>> if try_to_unmap_one() handles an hwpoisoned folio, then the head page is
>> marked with the poison bit.
>>
>> Therefore, convert the poisoned subpage checks to folio_test_hwpoison().
>>
>> No functional change intended, except that, while at it,
>> convert VM_BUG_* to VM_WARN_*.
>>
>> Acked-by: David Hildenbrand (Arm) <david@kernel.org>
>> Signed-off-by: Dev Jain <dev.jain@arm.com>
>
> Oops reviewed v2 by mistake. This LGTM so:
>
> Reviewed-by: Lorenzo Stoakes (ARM) <ljs@kernel.org>
>
Thanks for your review.
>> ---
>> mm/rmap.c | 13 +++++++++----
>> 1 file changed, 9 insertions(+), 4 deletions(-)
>>
>> diff --git a/mm/rmap.c b/mm/rmap.c
>> index 26166a6b8cb9b..2b74668f356d6 100644
>> --- a/mm/rmap.c
>> +++ b/mm/rmap.c
>> @@ -2122,10 +2122,11 @@ static bool try_to_unmap_one(struct folio *folio, struct vm_area_struct *vma,
>> bool anon = folio_test_anon(folio);
>>
>> /*
>> - * The try_to_unmap() is only passed a hugetlb page
>> - * in the case where the hugetlb page is poisoned.
>> + * The try_to_unmap() is only passed a hugetlb folio
>> + * in the case where the hugetlb folio contains a
>> + * poisoned page.
>> */
>> - VM_BUG_ON_PAGE(!PageHWPoison(subpage), subpage);
>> + VM_WARN_ON_FOLIO(!folio_test_hwpoison(folio), folio);
>
> Thanks for converting this also!
>
>> /*
>> * huge_pmd_unshare may unmap an entire PMD page.
>> * There is no way of knowing exactly which PMDs may
>> @@ -2204,7 +2205,11 @@ static bool try_to_unmap_one(struct folio *folio, struct vm_area_struct *vma,
>> /* Update high watermark before we lower rss */
>> update_hiwater_rss(mm);
>>
>> - if (PageHWPoison(subpage) && (flags & TTU_HWPOISON)) {
>> + /*
>> + * With TTU_HWPOISON, we only expect small folios or hugetlb
>> + * folios here for now.
>> + */
>> + if (folio_test_hwpoison(folio) && (flags & TTU_HWPOISON)) {
>
> As per v2 discussion, I feel this could be tightened up, maybe something like:
>
> /* unmap_poisoned_folio() only refs order-0 or hugetlb folios */
>
I can do this. But note that this series is in mm-unstable already - what should
I base the v4 on?
>> pteval = swp_entry_to_pte(make_hwpoison_entry(subpage));
>> if (folio_test_hugetlb(folio)) {
>> hugetlb_count_sub(folio_nr_pages(folio), mm);
>> --
>> 2.43.0
>>
>
> Cheers, Lorenzo
next prev parent reply other threads:[~2026-07-25 7:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-13 5:00 [PATCH v3 0/5] mm/rmap: Refactor try_to_unmap_one Dev Jain
2026-07-13 5:00 ` [PATCH v3 1/5] mm/rmap: convert page -> folio for hwpoison checks Dev Jain
2026-07-24 9:20 ` Lorenzo Stoakes (ARM)
2026-07-25 7:36 ` Dev Jain [this message]
2026-07-26 2:07 ` Andrew Morton
2026-07-26 8:22 ` Dev Jain
2026-07-13 5:00 ` [PATCH v3 2/5] mm/rmap: Add try_to_unmap_hugetlb_one Dev Jain
2026-07-24 10:39 ` Lorenzo Stoakes (ARM)
2026-07-25 8:47 ` Dev Jain
2026-07-13 5:00 ` [PATCH v3 3/5] mm/rmap: refactor some code around lazyfree folio unmapping Dev Jain
2026-07-13 5:00 ` [PATCH v3 4/5] mm/rmap: refactor anon folio unmap in try_to_unmap_one Dev Jain
2026-07-28 19:27 ` David Hildenbrand (Arm)
2026-07-13 5:00 ` [PATCH v3 5/5] mm/rmap: add anon folio unmap dispatcher Dev Jain
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=8d2f756a-12a2-43bb-8849-3e71c1ce5d8f@arm.com \
--to=dev.jain@arm.com \
--cc=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.com \
--cc=david@kernel.org \
--cc=harry@kernel.org \
--cc=jannh@google.com \
--cc=lance.yang@linux.dev \
--cc=liam@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=muchun.song@linux.dev \
--cc=osalvador@suse.de \
--cc=riel@surriel.com \
--cc=ryan.roberts@arm.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
all inboxes | Powered by JetHome®