From: Sasha Levin <sashal@kernel.org>
To: Lance Yang <lance.yang@linux.dev>
Cc: Sasha Levin <sashal@kernel.org>,
stable@vger.kernel.org, samarth.colleges@gmail.com,
akpm@linux-foundation.org, ljs@kernel.org, kas@kernel.org,
david@kernel.org, mgorman@techsingularity.net, 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,
bobbypowers@gmail.com, bgeffon@google.com,
dplotnikov@virtuozzo.com, dgilbert@interlog.com,
hughd@google.com, hannes@cmpxchg.org, cracauer@cons.org,
mcfadden8@llnl.gov, gokhale2@llnl.gov, xemul@openvz.org,
riel@surriel.com, shli@fb.com, jthoughton@google.com,
corbet@lwn.net, pbonzini@redhat.com, seanjc@google.com,
sj@kernel.org, ziy@nvidia.com, med08elkadiri@gmail.com
Subject: Re: [PATCH 6.18.y] mm/ksm: fix userfaultfd protection during merge and unmerge
Date: Fri, 20 Nov 2026 15:39:14 -0500 [thread overview]
Message-ID: <2026-11-20-1-daily-reply-0025@kernel.org> (raw)
In-Reply-To: <20261120082800.23727-1-lance.yang@linux.dev>
> Checked again. 6.18.y and 6.12.y have the soft-dirty fix now.
>
> We're just waiting on 6.6.y. Did the soft-dirty fix get missed in 6.6.y?
Not missed: 2efc6332f18b ("mm/ksm: keep soft-dirty when merging a page") is
queued for the next 6.6 release. Please send the v2 for 6.18, 6.12 and 6.6 now,
on top of the stable queue, together with the 6.1.y series.
--
Thanks,
Sasha
prev parent reply other threads:[~2026-11-20 20:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-10 1:04 FAILED: patch "[PATCH] mm/ksm: fix userfaultfd protection during merge and unmerge" failed to apply to 6.18-stable tree Sasha Levin
2026-11-11 8:28 ` [PATCH 6.18.y] mm/ksm: fix userfaultfd protection during merge and unmerge Lance Yang
2026-11-11 21:54 ` Sasha Levin
2026-11-12 1:42 ` Lance Yang
2026-11-20 8:28 ` Lance Yang
2026-11-20 20:39 ` 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-20-1-daily-reply-0025@kernel.org \
--to=sashal@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=david@kernel.org \
--cc=dgilbert@interlog.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=ljs@kernel.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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox