From: Sasha Levin <sashal@kernel.org>
To: stable@vger.kernel.org
Cc: "Sasha Levin" <sashal@kernel.org>,
"Andrea Arcangeli" <aarcange@redhat.com>,
"Hugh Dickins" <hughd@google.com>,
"Jason Gunthorpe" <jgg@ziepe.ca>,
"John Hubbard" <jhubbard@nvidia.com>,
"Matthew Wilcox (Oracle)" <willy@infradead.org>,
"Shuah Khan" <shuah@kernel.org>,
"Vlastimil Babka" <vbabka@kernel.org>,
"Mel Gorman" <mgorman@techsingularity.net>,
"Xu Xin" <xu.xin@linux.dev>,
"Chengming Zhou" <chengming.zhou@linux.dev>,
"Liam R. Howlett" <liam@infradead.org>,
"Mike Rapoport" <rppt@kernel.org>,
"Suren Baghdasaryan" <surenb@google.com>,
"Michal Hocko" <mhocko@suse.com>,
"Jérôme Glisse" <jglisse@redhat.com>,
"Peter Xu" <peterx@redhat.com>,
"Bobby Powers" <bobbypowers@gmail.com>,
"Brian Geffon" <bgeffon@google.com>,
"Denis Plotnikov" <dplotnikov@virtuozzo.com>,
"Doug Gilbert" <dgilbert@interlog.com>,
"Johannes Weiner" <hannes@cmpxchg.org>,
"Martin Cracauer" <cracauer@cons.org>,
"Marty McFadden" <mcfadden8@llnl.gov>,
"Maya Gokhale" <gokhale2@llnl.gov>,
"Pavel Emelyanov" <xemul@openvz.org>,
"Rik van Riel" <riel@surriel.com>, "Shaohua Li" <shli@fb.com>,
"James Houghton" <jthoughton@google.com>,
"Jonathan Corbet" <corbet@lwn.net>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Sean Christopherson" <seanjc@google.com>,
"SJ Park" <sj@kernel.org>, "Zi Yan" <ziy@nvidia.com>,
"Mohammed EL Kadiri" <med08elkadiri@gmail.com>,
"David Hildenbrand" <david@kernel.org>,
"Lance Yang" <lance.yang@linux.dev>
Subject: Re: [PATCH 6.1.y v2 0/3] mm/ksm: fix userfaultfd protection on 6.1
Date: Sat, 21 Nov 2026 22:38:44 -0500 [thread overview]
Message-ID: <2026-11-21-2-daily-reply-0001@kernel.org> (raw)
In-Reply-To: <20261121135653.3466-1-lance.yang@linux.dev>
> Could we take David's two KSM patches first for 6.1.y? Both cherry-pick
> cleanly. 6.1 already has FAULT_FLAG_UNSHARE, but KSM still breaks COW with
> a fake write fault.
>
> Patch 2 needs patch 1, and patch 3 needs both.
Queued the series for 6.1, and the v2 patches for 6.18, 6.12 and 6.6,
thanks.
--
Thanks,
Sasha
prev parent reply other threads:[~2026-11-22 3:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-10 1:17 FAILED: patch "[PATCH] mm/ksm: fix userfaultfd protection during merge and unmerge" failed to apply to 6.1-stable tree Sasha Levin
2026-11-11 10:50 ` [PATCH 6.1.y 0/3] mm/ksm: fix userfaultfd protection on 6.1 Lance Yang
2026-11-11 10:50 ` [PATCH 6.1.y 1/3] mm/ksm: simplify break_ksm() to not rely on VM_FAULT_WRITE Lance Yang
2026-11-11 10:50 ` [PATCH 6.1.y 2/3] mm/ksm: fix KSM COW breaking with userfaultfd-wp via FAULT_FLAG_UNSHARE Lance Yang
2026-11-11 10:50 ` [PATCH 6.1.y 3/3] mm/ksm: fix userfaultfd protection during merge and unmerge Lance Yang
2026-11-21 13:56 ` [PATCH 6.1.y v2 0/3] mm/ksm: fix userfaultfd protection on 6.1 Lance Yang
2026-11-21 13:56 ` [PATCH 6.1.y v2 1/3] mm/ksm: simplify break_ksm() to not rely on VM_FAULT_WRITE Lance Yang
2026-11-21 13:56 ` [PATCH 6.1.y v2 2/3] mm/ksm: fix KSM COW breaking with userfaultfd-wp via FAULT_FLAG_UNSHARE Lance Yang
2026-11-21 13:56 ` [PATCH 6.1.y v2 3/3] mm/ksm: fix userfaultfd protection during merge and unmerge Lance Yang
2026-11-22 3:38 ` Sasha Levin [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=2026-11-21-2-daily-reply-0001@kernel.org \
--to=sashal@kernel.org \
--cc=aarcange@redhat.com \
--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@interlog.com \
--cc=dplotnikov@virtuozzo.com \
--cc=gokhale2@llnl.gov \
--cc=hannes@cmpxchg.org \
--cc=hughd@google.com \
--cc=jgg@ziepe.ca \
--cc=jglisse@redhat.com \
--cc=jhubbard@nvidia.com \
--cc=jthoughton@google.com \
--cc=lance.yang@linux.dev \
--cc=liam@infradead.org \
--cc=mcfadden8@llnl.gov \
--cc=med08elkadiri@gmail.com \
--cc=mgorman@techsingularity.net \
--cc=mhocko@suse.com \
--cc=pbonzini@redhat.com \
--cc=peterx@redhat.com \
--cc=riel@surriel.com \
--cc=rppt@kernel.org \
--cc=seanjc@google.com \
--cc=shli@fb.com \
--cc=shuah@kernel.org \
--cc=sj@kernel.org \
--cc=stable@vger.kernel.org \
--cc=surenb@google.com \
--cc=vbabka@kernel.org \
--cc=willy@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox