mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dev Jain <dev.jain@arm.com>
To: "David Hildenbrand (Arm)" <david@kernel.org>,
	akpm@linux-foundation.org, ljs@kernel.org, chrisl@kernel.org,
	kasong@tencent.com, hughd@google.com, liam@infradead.org
Cc: riel@surriel.com, vbabka@kernel.org, harry@kernel.org,
	jannh@google.com, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org, rppt@kernel.org, surenb@google.com,
	mhocko@suse.com, qi.zheng@linux.dev, shakeel.butt@linux.dev,
	baohua@kernel.org, axelrasmussen@google.com, yuanchu@google.com,
	weixugc@google.com, shikemeng@huaweicloud.com, nphamcs@gmail.com,
	bhe@redhat.com, youngjun.park@lge.com,
	baolin.wang@linux.alibaba.com, pfalcato@suse.de,
	ryan.roberts@arm.com, anshuman.khandual@arm.com
Subject: Re: [PATCH v4 01/12] mm/rmap: convert page -> folio for hwpoison checks
Date: Wed, 10 Jun 2026 12:32:33 +0530	[thread overview]
Message-ID: <acb66e5d-188c-4239-95f8-172bbbb7f114@arm.com> (raw)
In-Reply-To: <f487d61c-844d-46b6-8522-375549d49346@kernel.org>



On 09/06/26 7:14 pm, David Hildenbrand (Arm) wrote:
> On 5/26/26 08:36, Dev Jain wrote:
>> If any page of a folio is poisoned, try_to_unmap() is called with the
>> intent to remove any mappings pointing to any part of the folio.
>>
>> Therefore, an hwpoison check on a single page does not make sense
>> (although everything works out because the memory-failure path sets
>> hwpoison on the head page too). Convert these checks to check whether
>> the folio has at least one hwpoisoned page.
> 
> I think the reasoning is different and should better be described:
> 
> 1) For hugetlb, we will always get subpage == head page (single PTE -> first PFN).
> 
> try_memory_failure_hugetlb()->try_memory_failure_hugetlb()->hugetlb_update_hwpoison()
> will do the folio_test_set_hwpoison().
> 
> folio_test_set_hwpoison() is the same as setting it on the head page.
> 
> For hugetlb, subpage==headpage
> 
> That's why PageHWPoison(subpage) used to work.
> 
> 
> 2) try_to_unmap() cannot handle large folios (besides hugetlb folios).
> 
> unmap_poisoned_folio() spells that out. That's why subpage==headpage right now.

Should have mentioned: subpage != headpage for contpte mapped hugetlb folios
on arm64.

But I think even in that case, hwpoison is not set on the specific pfn, it is
set only on the head page. So I think folio_test_hwpoison() would suffice.

> 
> 
> That's why PageHWPoison(subpage) used to work.
> 
>>
>> While at it, convert VM_BUG_* to VM_WARN_*.
>>
>> Signed-off-by: Dev Jain <dev.jain@arm.com>
>> ---
>>  mm/rmap.c | 9 +++++----
>>  1 file changed, 5 insertions(+), 4 deletions(-)
>>
>> diff --git a/mm/rmap.c b/mm/rmap.c
>> index fb3c351f8c458..430c91c8fe2ae 100644
>> --- a/mm/rmap.c
>> +++ b/mm/rmap.c
>> @@ -2116,10 +2116,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_contain_hwpoisoned_page(folio), folio);
> 
> I think we could also just use folio_test_hwpoison() here.
> 
>>  			/*
>>  			 * huge_pmd_unshare may unmap an entire PMD page.
>>  			 * There is no way of knowing exactly which PMDs may
>> @@ -2198,7 +2199,7 @@ 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)) {
>> +		if (folio_contain_hwpoisoned_page(folio) && (flags & TTU_HWPOISON)) {
>>  			pteval = swp_entry_to_pte(make_hwpoison_entry(subpage));
>>  			if (folio_test_hugetlb(folio)) {
>>  				hugetlb_count_sub(folio_nr_pages(folio), mm);
> 
> And here. Which might be cleaner, because folio_contain_hwpoisoned_page() is so
> far never called on hugetlb folios.
> 
> Because folio_set_has_hwpoisoned() is only ever used on THPs, not hugetlb. It
> would currently work, but the expectation so far is that these primitives are
> for small folios+thp, not hugetlb.
> 
> You could add a comment here, that with TTU_HWPOISON, we only ever expect small
> folios or hugetlb folios for now.
> 


  reply	other threads:[~2026-06-10  7:02 UTC|newest]

Thread overview: 56+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-26  6:36 [PATCH v4 00/12] Optimize anonymous large folio unmapping Dev Jain
2026-05-26  6:36 ` [PATCH v4 01/12] mm/rmap: convert page -> folio for hwpoison checks Dev Jain
2026-06-09 13:44   ` David Hildenbrand (Arm)
2026-06-10  7:02     ` Dev Jain [this message]
2026-06-10 12:13       ` David Hildenbrand (Arm)
2026-05-26  6:36 ` [PATCH v4 02/12] mm/rmap: Add try_to_unmap_hugetlb_one Dev Jain
2026-06-09 14:16   ` David Hildenbrand (Arm)
2026-06-18  7:44     ` Lance Yang
2026-06-18  7:55       ` David Hildenbrand (Arm)
2026-06-18  9:09         ` Lance Yang
2026-06-18  9:43           ` David Hildenbrand (Arm)
2026-06-18 10:01             ` Lance Yang
2026-06-22  8:13               ` Dev Jain
2026-06-22  8:14                 ` Lance Yang
2026-06-22  8:14                 ` Dev Jain
2026-06-22  8:17                   ` David Hildenbrand (Arm)
2026-06-24  5:50                     ` Dev Jain
2026-06-24  6:58                       ` Lance Yang
2026-06-23  8:40     ` Dev Jain
2026-06-23 11:49       ` David Hildenbrand (Arm)
2026-07-09  7:16   ` Garg, Shivank
2026-07-09  8:58     ` Dev Jain
2026-07-09  9:20       ` Garg, Shivank
2026-07-09  9:24         ` Dev Jain
2026-05-26  6:36 ` [PATCH v4 03/12] mm/rmap: refactor some code around lazyfree folio unmapping Dev Jain
2026-06-09 14:20   ` David Hildenbrand (Arm)
2026-06-23  8:42     ` Dev Jain
2026-06-29 12:30       ` David Hildenbrand (Arm)
2026-05-26  6:36 ` [PATCH v4 04/12] mm/memory: Batch set uffd-wp markers during zapping Dev Jain
2026-06-16 13:43   ` David Hildenbrand (Arm)
2026-06-23 10:01     ` Dev Jain
2026-06-27  9:00       ` Dev Jain
2026-07-07 13:47         ` David Hildenbrand (Arm)
2026-05-26  6:36 ` [PATCH v4 05/12] mm/rmap: batch unmap folios belonging to uffd-wp VMAs Dev Jain
2026-05-26  6:36 ` [PATCH v4 06/12] mm/swap: rename subpage->page in folio_dup_swap/folio_put_swap Dev Jain
2026-06-16 13:47   ` David Hildenbrand (Arm)
2026-05-26  6:36 ` [PATCH v4 07/12] mm/swapfile: Add batched version of folio_dup_swap Dev Jain
2026-06-16 13:50   ` David Hildenbrand (Arm)
2026-06-16 13:51   ` David Hildenbrand (Arm)
2026-05-26  6:36 ` [PATCH v4 08/12] mm/swapfile: Add batched version of folio_put_swap Dev Jain
2026-06-16 13:54   ` David Hildenbrand (Arm)
2026-06-23 10:03     ` Dev Jain
2026-05-26  6:36 ` [PATCH v4 09/12] mm/rmap: Add batched version of folio_try_share_anon_rmap_pte Dev Jain
2026-06-16 14:04   ` David Hildenbrand (Arm)
2026-06-23 10:05     ` Dev Jain
2026-05-26  6:36 ` [PATCH v4 10/12] mm/rmap: refactor anon folio unmap in try_to_unmap_one Dev Jain
2026-06-16 14:10   ` David Hildenbrand (Arm)
2026-06-23 11:01     ` Dev Jain
2026-05-26  6:36 ` [PATCH v4 11/12] mm/mprotect: drop 'sub' from page_anon_exclusive_sub_batch Dev Jain
2026-06-16 14:12   ` David Hildenbrand (Arm)
2026-06-23 11:02     ` Dev Jain
2026-05-26  6:36 ` [PATCH v4 12/12] mm/rmap: enable batch unmapping of anonymous folios Dev Jain
2026-05-28 16:50 ` [PATCH v4 00/12] Optimize anonymous large folio unmapping Dev Jain
2026-06-09 13:24 ` David Hildenbrand (Arm)
2026-06-09 14:18 ` David Hildenbrand (Arm)
2026-06-23 11:04   ` 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=acb66e5d-188c-4239-95f8-172bbbb7f114@arm.com \
    --to=dev.jain@arm.com \
    --cc=akpm@linux-foundation.org \
    --cc=anshuman.khandual@arm.com \
    --cc=axelrasmussen@google.com \
    --cc=baohua@kernel.org \
    --cc=baolin.wang@linux.alibaba.com \
    --cc=bhe@redhat.com \
    --cc=chrisl@kernel.org \
    --cc=david@kernel.org \
    --cc=harry@kernel.org \
    --cc=hughd@google.com \
    --cc=jannh@google.com \
    --cc=kasong@tencent.com \
    --cc=liam@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=ljs@kernel.org \
    --cc=mhocko@suse.com \
    --cc=nphamcs@gmail.com \
    --cc=pfalcato@suse.de \
    --cc=qi.zheng@linux.dev \
    --cc=riel@surriel.com \
    --cc=rppt@kernel.org \
    --cc=ryan.roberts@arm.com \
    --cc=shakeel.butt@linux.dev \
    --cc=shikemeng@huaweicloud.com \
    --cc=surenb@google.com \
    --cc=vbabka@kernel.org \
    --cc=weixugc@google.com \
    --cc=youngjun.park@lge.com \
    --cc=yuanchu@google.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

Powered by JetHome