From: Vlastimil Babka <vbabka@suse.cz>
To: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: Suren Baghdasaryan <surenb@google.com>,
"Liam R . Howlett" <Liam.Howlett@oracle.com>,
Matthew Wilcox <willy@infradead.org>,
"Paul E . McKenney" <paulmck@kernel.org>,
SeongJae Park <sj@kernel.org>,
Shakeel Butt <shakeel.butt@linux.dev>,
David Hildenbrand <david@redhat.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH v2 2/2] MAINTAINERS: add section for locking of mm's and VMAs
Date: Wed, 16 Apr 2025 16:40:44 +0200 [thread overview]
Message-ID: <23311d9f-ca6f-4dbe-a24d-a5ef244173d2@suse.cz> (raw)
In-Reply-To: <e6ed679a184ca444b20dfa77af96913fd8b5efa0.1744799282.git.lorenzo.stoakes@oracle.com>
On 4/16/25 12:38, Lorenzo Stoakes wrote:
> We place this under memory mapping as related to memory mapping
> abstractions in the form of mm_struct and vm_area_struct (VMA). Now we have
> separated out mmap/vma locking logic into the mmap_lock.c and mmap_lock.h
> files, so this should encapsulate the majority of the mm locking logic in
> the kernel.
>
> Suren is best placed to maintain this logic as the core architect of VMA
> locking as a whole.
>
> Signed-off-by: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
> Reviewed-by: Suren Baghdasaryan <surenb@google.com>
> Reviewed-by: Shakeel Butt <shakeel.butt@linux.dev>
> Acked-by: David Hildenbrand <david@redhat.com>
Acked-by: Vlastimil Babka <vbabka@suse.cz>
Thanks!
> ---
> MAINTAINERS | 16 ++++++++++++++++
> 1 file changed, 16 insertions(+)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 8d834514a047..03bbc41138c9 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -15595,6 +15595,22 @@ F: mm/vma_internal.h
> F: tools/testing/selftests/mm/merge.c
> F: tools/testing/vma/
>
> +MEMORY MAPPING - LOCKING
> +M: Andrew Morton <akpm@linux-foundation.org>
> +M: Suren Baghdasaryan <surenb@google.com>
> +M: Liam R. Howlett <Liam.Howlett@oracle.com>
> +M: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
> +R: Vlastimil Babka <vbabka@suse.cz>
> +R: Shakeel Butt <shakeel.butt@linux.dev>
> +L: linux-mm@kvack.org
> +S: Maintained
> +W: http://www.linux-mm.org
> +T: git git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
> +F: Documentation/mm/process_addrs.rst
> +F: include/linux/mmap_lock.h
> +F: include/trace/events/mmap_lock.h
> +F: mm/mmap_lock.c
> +
> MEMORY MAPPING - MADVISE (MEMORY ADVICE)
> M: Andrew Morton <akpm@linux-foundation.org>
> M: Liam R. Howlett <Liam.Howlett@oracle.com>
prev parent reply other threads:[~2025-04-16 14:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-16 10:38 [PATCH v2 0/2] separate out mmap_lock/VMA locking and update MAINTAINERS Lorenzo Stoakes
2025-04-16 10:38 ` [PATCH v2 1/2] mm: move mmap/vma locking logic into specific files Lorenzo Stoakes
2025-04-16 13:07 ` Liam R. Howlett
2025-04-16 14:39 ` Vlastimil Babka
2025-04-16 14:42 ` Lorenzo Stoakes
2025-04-16 10:38 ` [PATCH v2 2/2] MAINTAINERS: add section for locking of mm's and VMAs Lorenzo Stoakes
2025-04-16 13:08 ` Liam R. Howlett
2025-04-16 14:40 ` Vlastimil Babka [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=23311d9f-ca6f-4dbe-a24d-a5ef244173d2@suse.cz \
--to=vbabka@suse.cz \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=paulmck@kernel.org \
--cc=shakeel.butt@linux.dev \
--cc=sj@kernel.org \
--cc=surenb@google.com \
--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