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 v1 0/9] mm: backport sticky VMA flags and soft-dirty fix
Date: Fri, 15 May 2026 12:44:55 +0100 [thread overview]
Message-ID: <agcG2uKHhlt85FaV@lucifer> (raw)
In-Reply-To: <20260424211315.1072123-1-elaidya225@gmail.com>
Hi,
Just a heads up that I generally don't read kernel mail sent to my work address,
as I changed my email setup significantly and use ljs@kernel.org for everything
upstream!
Understandable given the original patches obviously used it but just FYI :)
Cheers, Lorenzo
On Sat, Apr 25, 2026 at 12:12:34AM +0300, Ahmed Elaidy wrote:
> This series backports the sticky VMA flags infrastructure and the
> VM_SOFTDIRTY-on-merge fix to linux-6.18.y.
>
> 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.
>
> Backport notes:
> - Non-trivial context conflicts were resolved in:
> - mm/mseal.c
> - mm/vma.c
> - Conflict resolution keeps upstream semantics; no intentional behavior
> changes beyond context adaptation for 6.18.y.
>
> Cc: stable@vger.kernel.org
>
>
>
> 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.53.0
next prev parent reply other threads:[~2026-05-15 11:44 UTC|newest]
Thread overview: 19+ 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
[not found] ` <CANaxB-xFcF7U=wJv8EqKy=j=-P3SN+sLQ9ytH8Ej69h03tqL8Q@mail.gmail.com>
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
2026-05-04 19:58 ` [PATCH v2] " Ahmed Elaidy
2026-05-15 11:44 ` Lorenzo Stoakes [this message]
2026-05-15 12:00 ` [PATCH 6.18.y v1 0/9] mm: backport sticky VMA flags and soft-dirty fix Lorenzo Stoakes
-- strict thread matches above, loose matches on Subject: below --
2026-04-24 21:04 Ahmed Elaidy
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=agcG2uKHhlt85FaV@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