From: Dev Jain <dev.jain@arm.com>
To: Lance Yang <lance.yang@linux.dev>,
"David Hildenbrand (Arm)" <david@kernel.org>
Cc: akpm@linux-foundation.org, ljs@kernel.org, chrisl@kernel.org,
kasong@tencent.com, hughd@google.com, liam@infradead.org,
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 02/12] mm/rmap: Add try_to_unmap_hugetlb_one
Date: Mon, 22 Jun 2026 13:43:26 +0530 [thread overview]
Message-ID: <dcfba95b-8cb0-4fa7-a21f-49b595eb92dd@arm.com> (raw)
In-Reply-To: <22613c23-612b-4de0-8731-00ad2da63eae@linux.dev>
On 18/06/26 3:31 pm, Lance Yang wrote:
>
>
> On 2026/6/18 17:43, David Hildenbrand (Arm) wrote:
>> On 6/18/26 11:09, Lance Yang wrote:
>>>
>>>
>>> On 2026/6/18 15:55, David Hildenbrand (Arm) wrote:
>>>>> return __rste_to_pte(pte_val(*ptep));
>>>>> }
>>>>>
>>>>>
>>>>> So plain ptep_get() can feed raw huge-entry bits into pte_pfn(), and the
>>>>> derived subpage can be wrong.
>>>>
>>>> Good question which impact that might have in practice?
>>>
>>> The subpage check can warn, but we still pass that subpage to
>>> make_hwpoison_entry(). So the hwpoison marker can end up with the
>>> wrong PFN?
>>>
>>> + subpage = folio_page(folio, pte_pfn(pteval) - folio_pfn(folio));
>>> + VM_WARN_ON(folio_page(folio, 0) != subpage);
>>> [...]
>>> + pteval = swp_entry_to_pte(make_hwpoison_entry(subpage));
>>
>> My s390x page table knowledge is a bit rusty.
>>
>> IIUC, it would be a problem if some PTE bits in segment/region entries (pmd/pud/
>> ...) would pass the
>>
>> pte_pfn(x) -> (pte_val(x) >> PAGE_SHIFT)
>>
>> check. I don't think this applies, because
>>
>> While
>> #define _SEGMENT_ENTRY_ORIGIN_LARGE ~0xfffffUL
>>
>> We also have
>>
>> #define _SEGMENT_ENTRY_ORIGIN ~0x7ffUL
>>
>> So these bits are not actually used.
>>
>> What __rste_to_pte() primarily does is reshuffling present bits etc.
>>
>> So using any other bits besides the PFN would be problematic I guess.
>>
>> Am I wrong or isn't the present bit already at a different location? For
>> prot-none hugetlb folios there might be a real issue, as the PTE present bit
>> corresponds to the PMD/PUD read-permission bit.
>>
>>
>> Oh my :)
>>
>> So yeah, we should probably fix that ahead of time unless I am missing
>> something? Good that we separate that hugetlb crap out.
>
> Yeah, looks like this was already there before the split. Should this
> be fixed separately?
Same bug is there in try_to_migrate_one(), check_pte(), remove_migration_pte()
and prot_none_hugetlb_entry() :)
next prev parent reply other threads:[~2026-06-22 8:13 UTC|newest]
Thread overview: 38+ 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
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 [this message]
2026-06-22 8:14 ` Lance Yang
2026-06-22 8:14 ` Dev Jain
2026-06-22 8:17 ` David Hildenbrand (Arm)
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-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-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-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-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-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-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)
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=dcfba95b-8cb0-4fa7-a21f-49b595eb92dd@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=lance.yang@linux.dev \
--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