From: Lance Yang <lance.yang@linux.dev>
To: Dev Jain <dev.jain@arm.com>
Cc: ziy@nvidia.com, baolin.wang@linux.alibaba.com,
Liam.Howlett@oracle.com, npache@redhat.com, ryan.roberts@arm.com,
baohua@kernel.org, ioworker0@gmail.com,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
akpm@linux-foundation.org, lorenzo.stoakes@oracle.com,
david@redhat.com
Subject: Re: [PATCH mm-new 1/1] mm/khugepaged: guard is_zero_pfn() calls with pte_present()
Date: Thu, 16 Oct 2025 14:26:52 +0800 [thread overview]
Message-ID: <8d88fb47-5318-433c-bb07-aeea4a025db8@linux.dev> (raw)
In-Reply-To: <17c4c5f9-6ac8-4914-838f-f511dfbf948f@arm.com>
On 2025/10/16 14:17, Dev Jain wrote:
>
> On 16/10/25 9:06 am, Lance Yang wrote:
>> From: Lance Yang <lance.yang@linux.dev>
>>
>> A non-present entry, like a swap PTE, contains completely different data
>> (swap type and offset). pte_pfn() doesn't know this, so if we feed it a
>> non-present entry, it will spit out a junk PFN.
>>
>> What if that junk PFN happens to match the zeropage's PFN by sheer
>> chance? While really unlikely, this would be really bad if it did.
>>
>> So, let's fix this potential bug by ensuring all calls to is_zero_pfn()
>> in khugepaged.c are properly guarded by a pte_present() check.
>>
>> Suggested-by: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
>> Signed-off-by: Lance Yang <lance.yang@linux.dev>
>> ---
>> mm/khugepaged.c | 13 ++++++++-----
>> 1 file changed, 8 insertions(+), 5 deletions(-)
>>
>> diff --git a/mm/khugepaged.c b/mm/khugepaged.c
>> index d635d821f611..0341c3d13e9e 100644
>> --- a/mm/khugepaged.c
>> +++ b/mm/khugepaged.c
>> @@ -516,7 +516,7 @@ static void release_pte_pages(pte_t *pte, pte_t
>> *_pte,
>> pte_t pteval = ptep_get(_pte);
>> unsigned long pfn;
>> - if (pte_none(pteval))
>> + if (!pte_present(pteval))
>> continue;
>> pfn = pte_pfn(pteval);
>> if (is_zero_pfn(pfn))
>> @@ -690,9 +690,10 @@ static void
>> __collapse_huge_page_copy_succeeded(pte_t *pte,
>> address += nr_ptes * PAGE_SIZE) {
>> nr_ptes = 1;
>> pteval = ptep_get(_pte);
>> - if (pte_none(pteval) || is_zero_pfn(pte_pfn(pteval))) {
>> + if (pte_none(pteval) ||
>> + (pte_present(pteval) && is_zero_pfn(pte_pfn(pteval)))) {
>> add_mm_counter(vma->vm_mm, MM_ANONPAGES, 1);
>> - if (is_zero_pfn(pte_pfn(pteval))) {
>> + if (!pte_none(pteval)) {
>
> Could save a level of indentation by saying
> if (pte_none(pteval))
> continue;
>
> That would make it crystal clear that we do nothing when pte is none,
> and we do something when pte is pointing to zero pfn.
Yes! That does look clearer ;)
I'll pick that up in the next spin, if one is needed.
>
> Reviewed-by: Dev Jain <dev.jain@arm.com>
Cheers!
>
>> /*
>> * ptl mostly unnecessary.
>> */
>> @@ -794,7 +795,8 @@ static int __collapse_huge_page_copy(pte_t *pte,
>> struct folio *folio,
>> unsigned long src_addr = address + i * PAGE_SIZE;
>> struct page *src_page;
>> - if (pte_none(pteval) || is_zero_pfn(pte_pfn(pteval))) {
>> + if (pte_none(pteval) ||
>> + (pte_present(pteval) && is_zero_pfn(pte_pfn(pteval)))) {
>> clear_user_highpage(page, src_addr);
>> continue;
>> }
>> @@ -1294,7 +1296,8 @@ static int hpage_collapse_scan_pmd(struct
>> mm_struct *mm,
>> goto out_unmap;
>> }
>> }
>> - if (pte_none(pteval) || is_zero_pfn(pte_pfn(pteval))) {
>> + if (pte_none(pteval) ||
>> + (pte_present(pteval) && is_zero_pfn(pte_pfn(pteval)))) {
>> ++none_or_zero;
>> if (!userfaultfd_armed(vma) &&
>> (!cc->is_khugepaged ||
next prev parent reply other threads:[~2025-10-16 6:27 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-16 3:36 [PATCH mm-new 1/1] mm/khugepaged: guard is_zero_pfn() calls with pte_present() Lance Yang
2025-10-16 5:34 ` Dev Jain
2025-10-16 5:59 ` Lance Yang
2025-10-16 6:15 ` Dev Jain
2025-10-16 6:17 ` Dev Jain
2025-10-16 6:26 ` Lance Yang [this message]
2025-10-17 1:27 ` Wei Yang
2025-10-17 8:11 ` David Hildenbrand
2025-10-17 8:37 ` Lance Yang
2025-10-17 8:43 ` David Hildenbrand
2025-10-17 8:47 ` Lance Yang
2025-10-17 9:35 ` Lorenzo Stoakes
2025-10-16 9:33 ` Wei Yang
2025-10-16 10:51 ` Lance Yang
2025-10-17 8:10 ` Baolin Wang
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=8d88fb47-5318-433c-bb07-aeea4a025db8@linux.dev \
--to=lance.yang@linux.dev \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=baohua@kernel.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=david@redhat.com \
--cc=dev.jain@arm.com \
--cc=ioworker0@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=npache@redhat.com \
--cc=ryan.roberts@arm.com \
--cc=ziy@nvidia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.