From: Mike Rapoport <rppt@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Lorenzo Stoakes <ljs@kernel.org>,
David Carlier <devnexen@gmail.com>,
David Hildenbrand <david@kernel.org>,
Heechan Kang <gganji11@naver.com>,
"Liam R. Howlett" <liam@infradead.org>,
Michael Bommarito <michael.bommarito@gmail.com>,
Peter Xu <peterx@redhat.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH v2 1/3] userfaultfd: verify VMA state across UFFDIO_COPY retry
Date: Mon, 8 Jun 2026 21:57:58 +0300 [thread overview]
Message-ID: <aicQtr1tbnhhqmtw@kernel.org> (raw)
In-Reply-To: <20260608093918.68ce9d7d5694380e3055e293@linux-foundation.org>
On Mon, Jun 08, 2026 at 09:39:18AM -0700, Andrew Morton wrote:
> On Mon, 8 Jun 2026 14:03:11 +0100 Lorenzo Stoakes <ljs@kernel.org> wrote:
>
> > > > > Fixes: 292411fda25b ("mm/userfaultfd: detect VMA type change after copy retry in mfill_copy_folio_retry()")
> > > > > Fixes: 6ab703034f14 ("userfaultfd: mfill_atomic(): remove retry logic")
> > > >
> > > > Did we want a Cc: Stable?
> > >
> > > Andrew adds it when applying.
> >
> > Hmm, I didn't think this always happened by default? :)
>
> Nope, adding cc:stable is manual, case-by-case and the -stable
> maintainers have been asked not to automatically backport MM patches
> which contain Fixes:.
>
> So this one snuck into mainline without the cc:stable tag.
>
> Thanks for noticing. Greg, Sasha: can we please add mainline's
> 85668fda932a ("userfaultfd: verify VMA state across UFFDIO_COPY retry")
> to the backporting pile?
There is no need to backport, both commits that 85668fda932a fixes are in
7.1.
--
Sincerely yours,
Mike.
next prev parent reply other threads:[~2026-06-08 18:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-27 18:47 [PATCH v2 0/3] userfaultfd: verify VMA state across UFFDIO_COPY retry Mike Rapoport
2026-05-27 18:47 ` [PATCH v2 1/3] " Mike Rapoport
2026-05-28 13:31 ` Lorenzo Stoakes
2026-05-28 14:41 ` Mike Rapoport
2026-05-28 21:04 ` Andrew Morton
2026-06-08 13:03 ` Lorenzo Stoakes
2026-06-08 16:39 ` Andrew Morton
2026-06-08 18:57 ` Mike Rapoport [this message]
2026-05-27 18:47 ` [PATCH v2 2/3] userfaultfd: refuse to __mfill_atomic_pte() for unsupported VMAs Mike Rapoport
2026-05-27 19:09 ` David CARLIER
2026-05-28 7:33 ` Mike Rapoport
2026-05-28 7:34 ` David CARLIER
2026-05-28 13:11 ` Lorenzo Stoakes
2026-05-27 18:47 ` [PATCH v2 3/3] userfaultfd: remove redundant check in vm_uffd_ops() Mike Rapoport
2026-05-28 13:10 ` Lorenzo Stoakes
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=aicQtr1tbnhhqmtw@kernel.org \
--to=rppt@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=david@kernel.org \
--cc=devnexen@gmail.com \
--cc=gganji11@naver.com \
--cc=gregkh@linuxfoundation.org \
--cc=liam@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=michael.bommarito@gmail.com \
--cc=peterx@redhat.com \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.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 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.