From: Lorenzo Stoakes <ljs@kernel.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Ahmed Elaidy <elaidya225@gmail.com>,
Andrei Vagin <avagin@gmail.com>,
stable@vger.kernel.org, akpm@linux-foundation.org,
linux-mm@kvack.org
Subject: Re: [PATCH 6.18.y v3] mm: fix VM_SOFTDIRTY propagation on VMA merge
Date: Fri, 15 May 2026 12:52:17 +0100 [thread overview]
Message-ID: <agcH4ve5jrc0iQWN@lucifer> (raw)
In-Reply-To: <2026051531-failing-nectar-83bf@gregkh>
On Fri, May 15, 2026 at 11:22:02AM +0200, Greg KH wrote:
> On Mon, May 04, 2026 at 10:54:47PM +0300, Ahmed Elaidy wrote:
> > During VMA merging, such as through mprotect(), VM_SOFTDIRTY flags could be
> > lost. This breaks tools relying on soft-dirty tracking, such as CRIU
> > incremental dump/restore.
> >
> > Upstream resolved this using a broader VM_STICKY infrastructure (commit
> > bf14d4a05387 "mm: propagate VM_SOFTDIRTY on merge"). To minimize churn and
> > risk in the stable 6.18.y tree, this patch skips backporting the entire
> > VM_STICKY series (9 patches). Instead, it introduces a minimal standalone fix.
>
> 9 patches is nothing. Please just backport the whole thing, especially
> as we will be maintaining this kernel for a long time. We want what is
> upstream for future issues/fixes, right?
FWIW, agreed!
>
> thanks,
>
> greg k-h
Cheers, Lorenzo
next prev parent reply other threads:[~2026-05-15 11:52 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-24 21:12 [PATCH 6.18.y v1 0/9] mm: backport sticky VMA flags and soft-dirty fix Ahmed Elaidy
2026-04-24 21:12 ` [PATCH v1 1/9] mm: introduce VM_MAYBE_GUARD and make visible in /proc/$pid/smaps Ahmed Elaidy
2026-04-24 21:12 ` [PATCH v1 2/9] mm: add atomic VMA flags and set VM_MAYBE_GUARD as such Ahmed Elaidy
2026-04-24 21:12 ` [PATCH v1 3/9] mm: update vma_modify_flags() to handle residual flags, document Ahmed Elaidy
2026-04-24 21:12 ` [PATCH v1 4/9] mm: implement sticky VMA flags Ahmed Elaidy
2026-04-24 21:12 ` [PATCH v1 5/9] mm: introduce copy-on-fork VMAs and make VM_MAYBE_GUARD one Ahmed Elaidy
2026-04-24 21:12 ` [PATCH v1 6/9] mm: set the VM_MAYBE_GUARD flag on guard region install Ahmed Elaidy
2026-04-24 21:12 ` [PATCH v1 7/9] tools/testing/vma: add VMA sticky userland tests Ahmed Elaidy
2026-04-24 21:12 ` [PATCH v1 8/9] mm: propagate VM_SOFTDIRTY on merge Ahmed Elaidy
2026-04-24 21:12 ` [PATCH v1 9/9] testing/selftests/mm: add soft-dirty merge self-test Ahmed Elaidy
2026-04-24 21:55 ` [PATCH 6.18.y v1 0/9] mm: backport sticky VMA flags and soft-dirty fix Andrei Vagin
2026-04-24 22:11 ` [PATCH v2] mm: fix VM_SOFTDIRTY propagation on VMA merge Ahmed Elaidy
2026-05-04 16:42 ` Andrei Vagin
2026-05-04 19:54 ` Ahmed Elaidy
2026-05-04 19:54 ` [PATCH 6.18.y v3] " Ahmed Elaidy
2026-05-15 9:22 ` Greg KH
2026-05-15 11:52 ` Lorenzo Stoakes [this message]
2026-05-04 19:58 ` [PATCH v2] " Ahmed Elaidy
2026-05-15 11:44 ` [PATCH 6.18.y v1 0/9] mm: backport sticky VMA flags and soft-dirty fix Lorenzo Stoakes
2026-05-15 12:00 ` 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=agcH4ve5jrc0iQWN@lucifer \
--to=ljs@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=avagin@gmail.com \
--cc=elaidya225@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-mm@kvack.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox