linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "David Hildenbrand (Arm)" <david@kernel.org>
To: Chris Down <chris@chrisdown.name>,
	Andrew Morton <akpm@linux-foundation.org>
Cc: Matthew Wilcox <willy@infradead.org>,
	kernel-team@fb.com, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH 1/2] mm/huge_memory: Fix use of NULL folio in move_pages_huge_pmd()
Date: Wed, 25 Feb 2026 16:23:29 +0100	[thread overview]
Message-ID: <7da49940-e1a4-4018-9db1-208411598e77@kernel.org> (raw)
In-Reply-To: <0b653dcd-842b-4360-bc1c-8fe779efbc23@kernel.org>

On 2/18/26 08:52, David Hildenbrand (Arm) wrote:
> On 2/18/26 04:45, Chris Down wrote:
>> move_pages_huge_pmd() handles UFFDIO_MOVE for both normal THPs and huge
>> zero pages. For the huge zero page path, src_folio is explicitly set to
>> NULL (used as a sentinel to skip folio operations like lock and rmap).
>>
>> In the huge zero page branch, src_folio is NULL, so folio_mk_pmd(NULL,
>> pgprot) passes NULL through folio_pfn() and page_to_pfn(). With
>> SPARSEMEM_VMEMMAP this silently produces a bogus PFN, installing a PMD
>> pointing to non-existent physical memory. On other memory models it
>> is a NULL dereference.
>>
>> Use page_folio(src_page) to obtain the valid huge zero folio from the
>> page, which was obtained from pmd_page() and remains valid throughout.
>>
>> Fixes: e3981db444a0 ("mm: add folio_mk_pmd()")
>> Cc: stable@vger.kernel.org
>> Signed-off-by: Chris Down <chris@chrisdown.name>
>> ---
>>   mm/huge_memory.c | 2 +-
>>   1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/mm/huge_memory.c b/mm/huge_memory.c
>> index 44ff8a648afd..fed57951a7cd 100644
>> --- a/mm/huge_memory.c
>> +++ b/mm/huge_memory.c
>> @@ -2794,7 +2794,7 @@ int move_pages_huge_pmd(struct mm_struct *mm,
>> pmd_t *dst_pmd, pmd_t *src_pmd, pm
>>           _dst_pmd = pmd_mkwrite(pmd_mkdirty(_dst_pmd), dst_vma);
>>       } else {
>>           src_pmdval = pmdp_huge_clear_flush(src_vma, src_addr, src_pmd);
>> -        _dst_pmd = folio_mk_pmd(src_folio, dst_vma->vm_page_prot);
>> +        _dst_pmd = folio_mk_pmd(page_folio(src_page), dst_vma-
>> >vm_page_prot);
>>       }
>>       set_pmd_at(mm, dst_addr, dst_pmd, _dst_pmd);
>>   
> 
> God this code is horrible.
> 
> Why can't we simply move the PMD like move_huge_pmd() would do and make
> this code less error prone?
> 
>     _dst_pmd = src_pmdval;
> 
> According to validate_move_areas(), the permissions of both VMAs are equal.
> 
> 
> We might have to handle it just like move_huge_pmd():
> 
>     _dst_pmd = move_soft_dirty_pmd(src_pmdval);
> 
> To also set the softdirty bit.
> 
> Then, we would want to just clear uffd.
> 
>     _dst_pmd = move_soft_dirty_pmd(src_pmdval);
>     _dst_pmd = clear_uffd_wp_pmd(_dst_pmd);
> 

Chris, do you have time to follow up, or should I look into it? The
issue looks quite bad, so we should tackle it ASAP.

-- 
Cheers,

David


      reply	other threads:[~2026-02-25 15:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-18  3:45 Chris Down
2026-02-18  7:52 ` David Hildenbrand (Arm)
2026-02-25 15:23   ` David Hildenbrand (Arm) [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=7da49940-e1a4-4018-9db1-208411598e77@kernel.org \
    --to=david@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=chris@chrisdown.name \
    --cc=kernel-team@fb.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=stable@vger.kernel.org \
    --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