[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <cover.1744720574.git.lorenzo.stoakes@oracle.com>
Date: Tue, 15 Apr 2025 14:10:44 +0100
From: Lorenzo Stoakes <lorenzo.stoakes@...cle.com>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: Suren Baghdasaryan <surenb@...gle.com>,
"Liam R . Howlett" <Liam.Howlett@...cle.com>,
Vlastimil Babka <vbabka@...e.cz>, Matthew Wilcox <willy@...radead.org>,
"Paul E . McKenney" <paulmck@...nel.org>,
SeongJae Park <sj@...nel.org>, linux-kernel@...r.kernel.org,
linux-mm@...ck.org
Subject: [PATCH 0/2] separate out mmap_lock/VMA locking and update MAINTAINERS
Separate out mmap_lock and VMA locking logic from include/linux/mm.h and
mm/memory.c and place it in the existing mm/mmap.lock.c and
include/linux/mmap_lock.h files.
This both provides separation of concerns and allows us to correctly assign
maintainership based on file contents.
We then go on to add an entry to MAINTAINERS adding the appropriate people
as maintainers and reviewers of this code.
This was first raised in the patch adding tracing files to the MEMORY
MAPPING in [0], kindly pointed out by SJ in [1]. This series implements the
suggested changes.
[0]: https://lore.kernel.org/all/20250411173328.8172-1-Liam.Howlett@oracle.com/
[1]: https://lore.kernel.org/all/20250411174734.51719-1-sj@kernel.org/
Lorenzo Stoakes (2):
mm: move mmap/vma locking logic into specific files
MAINTAINERS: add section for locking of mm's and VMAs
MAINTAINERS | 15 +++
include/linux/mm.h | 231 +---------------------------------
include/linux/mmap_lock.h | 227 +++++++++++++++++++++++++++++++++
mm/memory.c | 252 -------------------------------------
mm/mmap_lock.c | 255 ++++++++++++++++++++++++++++++++++++++
6 files changed, 501 insertions(+), 479 deletions(-)
create mode 100644 include/linux/vma.h
--
2.49.0
Powered by blists - more mailing lists