From: Lorenzo Stoakes <ljs@kernel.org>
To: Ahmed Elaidy <elaidya225@gmail.com>
Cc: stable@vger.kernel.org, linux-mm@kvack.org,
akpm@linux-foundation.org, avagin@gmail.com
Subject: Re: [PATCH 6.18.y v4 0/9] mm: backport sticky VMA flags and soft-dirty fix
Date: Thu, 25 Jun 2026 15:16:05 +0100 [thread overview]
Message-ID: <aj04FzkKa-9kqVrJ@lucifer> (raw)
In-Reply-To: <20260515124218.151966-2-elaidya225@gmail.com>
On Fri, May 15, 2026 at 03:42:10PM +0300, Ahmed Elaidy wrote:
> This series backports the sticky VMA flags infrastructure and the
> VM_SOFTDIRTY-on-merge fix to linux-6.18.y.
Thanks again for doing this Ahmed! :)
Cheers, Lorenzo
>
> Motivation: CRIU incremental dump/restore can hit a missing-parent-pagemap
> failure when VM_SOFTDIRTY is lost during VMA merge operations.
>
> Patch 8 is the target fix:
> mm: propagate VM_SOFTDIRTY on merge
>
> The preceding patches provide required dependencies on 6.18.y and are included
> to preserve upstream behavior, as requested by maintainers for stable backports.
>
> Changes since v3:
> - Reverted to sending the full 9-patch series as requested by Greg KH and Lorenzo.
> - Updated Lorenzo's email to ljs@kernel.org across all patches.
> - Added Cc: stable@vger.kernel.org # 6.18.x to all patches.
> - Added Fixes tag for soft-dirty merging in Patch 8.
>
> Lorenzo Stoakes (9):
> mm: introduce VM_MAYBE_GUARD and make visible in /proc/$pid/smaps
> mm: add atomic VMA flags and set VM_MAYBE_GUARD as such
> mm: update vma_modify_flags() to handle residual flags, document
> mm: implement sticky VMA flags
> mm: introduce copy-on-fork VMAs and make VM_MAYBE_GUARD one
> mm: set the VM_MAYBE_GUARD flag on guard region install
> tools/testing/vma: add VMA sticky userland tests
> mm: propagate VM_SOFTDIRTY on merge
> testing/selftests/mm: add soft-dirty merge self-test
>
> Documentation/filesystems/proc.rst | 5 +-
> fs/proc/task_mmu.c | 1 +
> include/linux/mm.h | 100 +++++++++++++++++
> include/trace/events/mmflags.h | 1 +
> mm/khugepaged.c | 71 +++++++-----
> mm/madvise.c | 24 +++--
> mm/memory.c | 14 +--
> mm/mlock.c | 2 +-
> mm/mprotect.c | 2 +-
> mm/mseal.c | 7 +-
> mm/vma.c | 81 +++++++-------
> mm/vma.h | 138 +++++++++++++++++-------
> tools/testing/selftests/mm/soft-dirty.c | 127 +++++++++++++++++++++-
> tools/testing/vma/vma.c | 92 ++++++++++++++--
> tools/testing/vma/vma_internal.h | 49 +++++++++
> 15 files changed, 579 insertions(+), 135 deletions(-)
>
> --
> 2.54.0
>
prev parent reply other threads:[~2026-06-25 14:16 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-15 12:42 [PATCH 6.18.y v4 0/9] mm: backport sticky VMA flags and soft-dirty fix Ahmed Elaidy
2026-05-15 12:42 ` [PATCH v4 1/9] mm: introduce VM_MAYBE_GUARD and make visible in /proc/$pid/smaps Ahmed Elaidy
2026-06-25 11:29 ` Patch "mm: introduce VM_MAYBE_GUARD and make visible in /proc/$pid/smaps" has been added to the 6.18-stable tree gregkh
2026-05-15 12:42 ` [PATCH v4 2/9] mm: add atomic VMA flags and set VM_MAYBE_GUARD as such Ahmed Elaidy
2026-06-25 11:29 ` Patch "mm: add atomic VMA flags and set VM_MAYBE_GUARD as such" has been added to the 6.18-stable tree gregkh
2026-05-15 12:42 ` [PATCH v4 3/9] mm: update vma_modify_flags() to handle residual flags, document Ahmed Elaidy
2026-06-25 11:29 ` Patch "mm: update vma_modify_flags() to handle residual flags, document" has been added to the 6.18-stable tree gregkh
2026-05-15 12:42 ` [PATCH v4 4/9] mm: implement sticky VMA flags Ahmed Elaidy
2026-06-25 11:29 ` Patch "mm: implement sticky VMA flags" has been added to the 6.18-stable tree gregkh
2026-05-15 12:42 ` [PATCH v4 5/9] mm: introduce copy-on-fork VMAs and make VM_MAYBE_GUARD one Ahmed Elaidy
2026-06-25 11:29 ` Patch "mm: introduce copy-on-fork VMAs and make VM_MAYBE_GUARD one" has been added to the 6.18-stable tree gregkh
2026-05-15 12:42 ` [PATCH v4 6/9] mm: set the VM_MAYBE_GUARD flag on guard region install Ahmed Elaidy
2026-06-25 11:29 ` Patch "mm: set the VM_MAYBE_GUARD flag on guard region install" has been added to the 6.18-stable tree gregkh
2026-05-15 12:42 ` [PATCH v4 7/9] tools/testing/vma: add VMA sticky userland tests Ahmed Elaidy
2026-05-15 12:42 ` [PATCH v4 8/9] mm: propagate VM_SOFTDIRTY on merge Ahmed Elaidy
2026-06-25 11:29 ` Patch "mm: propagate VM_SOFTDIRTY on merge" has been added to the 6.18-stable tree gregkh
2026-05-15 12:42 ` [PATCH v4 9/9] testing/selftests/mm: add soft-dirty merge self-test Ahmed Elaidy
2026-06-25 11:29 ` Patch "testing/selftests/mm: add soft-dirty merge self-test" has been added to the 6.18-stable tree gregkh
[not found] ` <2026061632-papaya-handwoven-d010@gregkh>
2026-06-19 15:29 ` [PATCH 6.18.y v4 0/9] mm: backport sticky VMA flags and soft-dirty fix Ahmed Elaidy
2026-06-25 14:16 ` Lorenzo Stoakes [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=aj04FzkKa-9kqVrJ@lucifer \
--to=ljs@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=avagin@gmail.com \
--cc=elaidya225@gmail.com \
--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