From: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: David Hildenbrand <david@kernel.org>,
"Liam R . Howlett" <Liam.Howlett@oracle.com>,
Vlastimil Babka <vbabka@suse.cz>, Mike Rapoport <rppt@kernel.org>,
Suren Baghdasaryan <surenb@google.com>,
Michal Hocko <mhocko@suse.com>, Jann Horn <jannh@google.com>,
Pedro Falcato <pfalcato@suse.de>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] make VM_SOFTDIRTY a sticky VMA flag
Date: Fri, 14 Nov 2025 17:53:17 +0000 [thread overview]
Message-ID: <cover.1763142412.git.lorenzo.stoakes@oracle.com> (raw)
Currently we set VM_SOFTDIRTY when a new mapping is set up (whether by
establishing a new VMA, or via merge) as implemented in __mmap_complete()
and do_brk_flags().
However, when performing a merge of existing mappings such as when
performing mprotect(), we may lose the VM_SOFTDIRTY flag.
Lorenzo Stoakes (2):
mm: propagate VM_SOFTDIRTY on merge
testing/selftests/mm: add soft-dirty merge self-test
include/linux/mm.h | 23 ++++++-----
tools/testing/selftests/mm/soft-dirty.c | 51 ++++++++++++++++++++++++-
tools/testing/vma/vma_internal.h | 23 ++++++-----
3 files changed, 72 insertions(+), 25 deletions(-)
--
2.51.0
next reply other threads:[~2025-11-14 17:53 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-14 17:53 Lorenzo Stoakes [this message]
2025-11-14 17:53 ` [PATCH 1/2] mm: propagate VM_SOFTDIRTY on merge Lorenzo Stoakes
2025-11-17 4:39 ` Anshuman Khandual
2025-11-17 11:34 ` Lorenzo Stoakes
2025-11-17 14:25 ` David Hildenbrand (Red Hat)
2025-11-17 15:35 ` Lorenzo Stoakes
2025-11-17 15:47 ` Pedro Falcato
2025-11-17 15:53 ` Lorenzo Stoakes
2025-11-17 16:05 ` Liam R. Howlett
2025-11-14 17:53 ` [PATCH 2/2] testing/selftests/mm: add soft-dirty merge self-test Lorenzo Stoakes
2025-11-17 14:44 ` David Hildenbrand (Red Hat)
2025-11-17 15:15 ` Lorenzo Stoakes
2025-11-14 21:53 ` [PATCH 0/2] make VM_SOFTDIRTY a sticky VMA flag Andrew Morton
2025-11-17 11:41 ` Lorenzo Stoakes
2025-11-17 0:53 ` Andrei Vagin
2025-11-17 4:37 ` Anshuman Khandual
2025-11-17 11:32 ` Lorenzo Stoakes
2025-11-17 18:26 ` Andrei Vagin
2025-11-17 19:57 ` Lorenzo Stoakes
2025-11-19 13:09 ` Cyrill Gorcunov
2025-11-19 17:21 ` 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=cover.1763142412.git.lorenzo.stoakes@oracle.com \
--to=lorenzo.stoakes@oracle.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=david@kernel.org \
--cc=jannh@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=pfalcato@suse.de \
--cc=rppt@kernel.org \
--cc=surenb@google.com \
--cc=vbabka@suse.cz \
/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.