linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Suren Baghdasaryan <surenb@google.com>,
	"Liam R . Howlett" <Liam.Howlett@oracle.com>,
	Vlastimil Babka <vbabka@suse.cz>,
	Matthew Wilcox <willy@infradead.org>,
	"Paul E . McKenney" <paulmck@kernel.org>,
	SeongJae Park <sj@kernel.org>,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: [PATCH 0/2] separate out mmap_lock/VMA locking and update MAINTAINERS
Date: Tue, 15 Apr 2025 14:10:44 +0100	[thread overview]
Message-ID: <cover.1744720574.git.lorenzo.stoakes@oracle.com> (raw)

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


             reply	other threads:[~2025-04-15 13:11 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-15 13:10 Lorenzo Stoakes [this message]
2025-04-15 13:10 ` [PATCH 1/2] mm: move mmap/vma locking logic into specific files Lorenzo Stoakes
2025-04-15 16:06   ` Suren Baghdasaryan
2025-04-15 16:07     ` Suren Baghdasaryan
2025-04-16  7:32       ` Lorenzo Stoakes
2025-04-15 17:58     ` Paul E. McKenney
2025-04-16  7:31       ` Lorenzo Stoakes
2025-04-16  7:30     ` Lorenzo Stoakes
2025-04-15 13:10 ` [PATCH 2/2] MAINTAINERS: add section for locking of mm's and VMAs Lorenzo Stoakes
2025-04-15 13:25   ` David Hildenbrand
2025-04-16  7:33     ` Lorenzo Stoakes
2025-04-16  8:07       ` David Hildenbrand
2025-04-15 15:37   ` Liam R. Howlett
2025-04-15 15:43     ` Lorenzo Stoakes
2025-04-15 16:14       ` Suren Baghdasaryan
2025-04-16  7:36         ` Lorenzo Stoakes
2025-04-15 18:00       ` Shakeel Butt
2025-04-16  6:47         ` 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.1744720574.git.lorenzo.stoakes@oracle.com \
    --to=lorenzo.stoakes@oracle.com \
    --cc=Liam.Howlett@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=paulmck@kernel.org \
    --cc=sj@kernel.org \
    --cc=surenb@google.com \
    --cc=vbabka@suse.cz \
    --cc=willy@infradead.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