All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lance Yang <lance.yang@linux.dev>
To: "Lorenzo Stoakes (ARM)" <ljs@kernel.org>
Cc: akpm@linux-foundation.org, david@kernel.org, xu.xin@linux.dev,
	chengming.zhou@linux.dev, liam@infradead.org, vbabka@kernel.org,
	rppt@kernel.org, surenb@google.com, mhocko@suse.com,
	jglisse@redhat.com, aarcange@redhat.com, peterx@redhat.com,
	kas@kernel.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	bobbypowers@gmail.com, bgeffon@google.com,
	dplotnikov@virtuozzo.com, dgilbert@redhat.com, hughd@google.com,
	hannes@cmpxchg.org, kirill@shutemov.name, cracauer@cons.org,
	mcfadden8@llnl.gov, gokhale2@llnl.gov, mgorman@suse.de,
	mike.kravetz@oracle.com, rppt@linux.vnet.ibm.com,
	xemul@openvz.org, riel@redhat.com, shli@fb.com,
	jthoughton@google.com, corbet@lwn.net, pbonzini@redhat.com,
	seanjc@google.com, sj@kernel.org, ziy@nvidia.com,
	stable@vger.kernel.org, samarth.colleges@gmail.com,
	med08elkadiri@gmail.com
Subject: Re: [PATCH] mm/ksm: fix userfaultfd protection during merge and unmerge
Date: Mon, 26 Oct 2026 23:18:06 +0800	[thread overview]
Message-ID: <a33247c5-4881-401e-aa1c-0de05820c8d5@linux.dev> (raw)
In-Reply-To: <at9d4XJUIM8SgBDs@gremlin>



On 2026/10/26 22:27, Lorenzo Stoakes (ARM) wrote:
> On Mon, Oct 26, 2026 at 09:00:54PM +0800, Lance Yang wrote:
>> KSM loses userfaultfd protection when replace_page() builds a new PTE
>> from vma->vm_page_prot. Dropping its uffd bit lets a subsequent write go
>> through ordinary COW instead of userfaultfd write protection handling. For
>> RWP, a merged page also becomes readable without faulting.
> 
> I feel we probably shouldn't have allowed an extension to UFFD while it's still
> fundamentally a broken feature :))
> 
> Which is evidenced by the SLEW of AI bug reports, and human-reported bug
> reports, and endless history of bug reports and it infecting the rest of mm,
> etc. etc. /rant

Heh, UFFD isn't winning you over today :D

>>
>> Keeping the uffd bit and restoring PAGE_NONE fixes merging, but we also
>> have to handle unmerging. An existing KSM page can be protected with RWP
>> before MADV_UNMERGEABLE, so unmerging already needs fixing independently
>> of preserving RWP during merging.
>>
>> Unsharing replaces a shared page with a private one and should leave
>> userfaultfd protection in place, as do_wp_page() already does for write
>> protection. Currently, an unshare fault reaches do_uffd_rwp() before it
>> can proceed to do_wp_page().
>>
>> - With synchronous RWP, handle_userfault() returns VM_FAULT_SIGBUS.
>>    break_ksm() then reports success with a KSM page still merged.
>>
>> - With asynchronous RWP, protection is cleared before unsharing.
>>
>> Preserve the uffd bit when merging, and restore PAGE_NONE for RWP. Let
>> FAULT_FLAG_UNSHARE skip RWP fault handling and keep PAGE_NONE on each
>> private copy as well. Unsharing can then complete with RWP still armed
>> for a subsequent access.
>>
>> Fixes: 63b2d4174c4a ("userfaultfd: wp: add the writeprotect API to userfaultfd ioctl")
>> Fixes: 2d427bb01639 ("mm/userfaultfd: add RWP fault delivery and expose UFFDIO_REGISTER_MODE_RWP")
>> Link: https://lore.kernel.org/all/20261019010934.697895-1-samarth.colleges@gmail.com/
>> Link: https://lore.kernel.org/all/20261020055518.36087-1-lance.yang@linux.dev/
>> Cc: stable@vger.kernel.org
>> Co-developed-by: Samarth Narang <samarth.colleges@gmail.com>
>> Signed-off-by: Samarth Narang <samarth.colleges@gmail.com>
>> Signed-off-by: Lance Yang <lance.yang@linux.dev>
> 
> Looks sensible to me so:
> 
> Acked-by: Lorenzo Stoakes (ARM) <ljs@kernel.org>

Really appreciated!

>> ---
>>   mm/ksm.c    |  8 +++++++-
>>   mm/memory.c | 14 ++++++++++----
>>   2 files changed, 17 insertions(+), 5 deletions(-)
>>
>> diff --git a/mm/ksm.c b/mm/ksm.c
>> index 910a1307ac9f..d6f736a1aa2f 100644
>> --- a/mm/ksm.c
>> +++ b/mm/ksm.c
>> @@ -34,6 +34,7 @@
>>   #include <linux/memory.h>
>>   #include <linux/mmu_notifier.h>
>>   #include <linux/swap.h>
>> +#include <linux/userfaultfd_k.h>
>>   #include <linux/ksm.h>
>>   #include <linux/hashtable.h>
>>   #include <linux/freezer.h>
>> @@ -1463,9 +1464,14 @@ static int replace_page(struct vm_area_struct *vma, struct page *page,
>>   		dec_mm_counter(mm, MM_ANONPAGES);
>>   	}
>>
>> -	/* Preserve soft-dirty when replacing the page. */
>> +	/* Preserve soft-dirty and uffd protection when replacing the page. */
>>   	if (pte_soft_dirty(orig_pte))
>>   		newpte = pte_mksoft_dirty(newpte);
>> +	if (pte_uffd(orig_pte)) {
>> +		newpte = pte_mkuffd(newpte);
>> +		if (userfaultfd_rwp(vma))
>> +			newpte = pte_modify(newpte, PAGE_NONE);
> 
> OK, so by definition, RWP pages are protnone, and this resets it correctly.

Right, we need PAGE_NONE back as well as the uffd bit :)

>> +	}
>>
>>   	flush_cache_page(vma, addr, pte_pfn(ptep_get(ptep)));
>>   	/*
>> diff --git a/mm/memory.c b/mm/memory.c
>> index 6a93b7fa48b2..99439a7afa63 100644
>> --- a/mm/memory.c
>> +++ b/mm/memory.c
>> @@ -4122,8 +4122,11 @@ static vm_fault_t wp_page_copy(struct vm_fault *vmf)
>>   		if (unlikely(unshare)) {
>>   			if (pte_soft_dirty(vmf->orig_pte))
>>   				entry = pte_mksoft_dirty(entry);
>> -			if (pte_uffd(vmf->orig_pte))
>> +			if (pte_uffd(vmf->orig_pte)) {
>>   				entry = pte_mkuffd(entry);
>> +				if (userfaultfd_rwp(vma))
>> +					entry = pte_modify(entry, PAGE_NONE);
>> +			}
> 
> Could this be abstracted? You're doing the same pattern here, which also exists
> in copy_present_page() and presumably many other places.
> 
> But maybe that's one for a follow up?

Yeah, a helper would be nice here. I'd keep this fix small and do that
as a follow-up :D

Cheers, Lance

>>   		} else {
>>   			entry = maybe_mkwrite(pte_mkdirty(entry), vma);
>>   		}
>> @@ -6659,9 +6662,12 @@ static vm_fault_t handle_pte_fault(struct vm_fault *vmf)
>>   		 * VM_UFFD_RWP VMA, a protnone PTE without the uffd bit is
>>   		 * NUMA hinting and must still fall through to do_numa_page().
>>   		 */
>> -		if (userfaultfd_pte_rwp(vmf->vma, vmf->orig_pte))
>> -			return do_uffd_rwp(vmf);
>> -		return do_numa_page(vmf);
>> +		if (userfaultfd_pte_rwp(vmf->vma, vmf->orig_pte)) {
>> +			if (!(vmf->flags & FAULT_FLAG_UNSHARE))
>> +				return do_uffd_rwp(vmf);
>> +		} else {
>> +			return do_numa_page(vmf);
>> +		}
>>   	}
>>
>>   	spin_lock(vmf->ptl);
>> --
>> 2.49.0
>>
> 
> --
> Cheers, Lorenzo



  reply	other threads:[~2026-10-26 15:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-26 13:00 [PATCH] mm/ksm: fix userfaultfd protection during merge and unmerge Lance Yang
2026-10-26 14:27 ` Lorenzo Stoakes (ARM)
2026-10-26 15:18   ` Lance Yang [this message]
2026-10-27 12:11 ` Kiryl Shutsemau
2026-10-27 12:14   ` David Hildenbrand (Arm)
2026-10-27 12:15 ` 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=a33247c5-4881-401e-aa1c-0de05820c8d5@linux.dev \
    --to=lance.yang@linux.dev \
    --cc=aarcange@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=bgeffon@google.com \
    --cc=bobbypowers@gmail.com \
    --cc=chengming.zhou@linux.dev \
    --cc=corbet@lwn.net \
    --cc=cracauer@cons.org \
    --cc=david@kernel.org \
    --cc=dgilbert@redhat.com \
    --cc=dplotnikov@virtuozzo.com \
    --cc=gokhale2@llnl.gov \
    --cc=hannes@cmpxchg.org \
    --cc=hughd@google.com \
    --cc=jglisse@redhat.com \
    --cc=jthoughton@google.com \
    --cc=kas@kernel.org \
    --cc=kirill@shutemov.name \
    --cc=liam@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=ljs@kernel.org \
    --cc=mcfadden8@llnl.gov \
    --cc=med08elkadiri@gmail.com \
    --cc=mgorman@suse.de \
    --cc=mhocko@suse.com \
    --cc=mike.kravetz@oracle.com \
    --cc=pbonzini@redhat.com \
    --cc=peterx@redhat.com \
    --cc=riel@redhat.com \
    --cc=rppt@kernel.org \
    --cc=rppt@linux.vnet.ibm.com \
    --cc=samarth.colleges@gmail.com \
    --cc=seanjc@google.com \
    --cc=shli@fb.com \
    --cc=sj@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=surenb@google.com \
    --cc=vbabka@kernel.org \
    --cc=xemul@openvz.org \
    --cc=xu.xin@linux.dev \
    --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.