From: "David Hildenbrand (Arm)" <david@kernel.org>
To: Kiryl Shutsemau <kas@kernel.org>, Lance Yang <lance.yang@linux.dev>
Cc: akpm@linux-foundation.org, xu.xin@linux.dev,
chengming.zhou@linux.dev, ljs@kernel.org, liam@infradead.org,
vbabka@kernel.org, rppt@kernel.org, surenb@google.com,
mhocko@suse.com, jglisse@redhat.com, aarcange@redhat.com,
peterx@redhat.com, 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,
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: Tue, 27 Oct 2026 13:14:02 +0100 [thread overview]
Message-ID: <85fb6a33-5c41-4e25-8bdc-ac01c60b4ecd@kernel.org> (raw)
In-Reply-To: <auCTv9O6F1JPyOAu@thinkstation>
On 10/27/26 13:11, Kiryl Shutsemau 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.
>>
>> 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>
>
> Thanks for fixing this:
>
> Reviewed-by: Kiryl Shutsemau (Meta) <kas@kernel.org>
>
>> @@ -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. */
>
> Small nit: the period at the end of a single-line comment looks odd to
> me. Am I the only one?
I think you are. :)
I would complain if something looks like a sentence but doesn't end with a period.
It would be different it it's not actually a full sentence.
/* preserve soft-dirty */
--
Cheers,
David
next prev parent reply other threads:[~2026-10-27 12:14 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
2026-10-27 12:11 ` Kiryl Shutsemau
2026-10-27 12:14 ` David Hildenbrand (Arm) [this message]
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=85fb6a33-5c41-4e25-8bdc-ac01c60b4ecd@kernel.org \
--to=david@kernel.org \
--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=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=lance.yang@linux.dev \
--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.