linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: David Hildenbrand <david@redhat.com>
To: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	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: Re: [PATCH 2/2] MAINTAINERS: add section for locking of mm's and VMAs
Date: Wed, 16 Apr 2025 10:07:50 +0200	[thread overview]
Message-ID: <a58050f9-726e-48e8-88ca-8d0d96bafb61@redhat.com> (raw)
In-Reply-To: <039f7b19-259d-44f0-a96e-618240317f73@lucifer.local>

On 16.04.25 09:33, Lorenzo Stoakes wrote:
> On Tue, Apr 15, 2025 at 03:25:09PM +0200, David Hildenbrand wrote:
>> On 15.04.25 15:10, 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>
>>> ---
>>>    MAINTAINERS | 15 +++++++++++++++
>>>    1 file changed, 15 insertions(+)
>>>
>>> diff --git a/MAINTAINERS b/MAINTAINERS
>>> index 8d834514a047..ce55676a16a4 100644
>>> --- a/MAINTAINERS
>>> +++ b/MAINTAINERS
>>> @@ -15595,6 +15595,21 @@ 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>
>>> +R:	Liam R. Howlett <Liam.Howlett@oracle.com>
>>> +R:	Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
>>> +R:	Vlastimil Babka <vbabka@suse.cz>
>>> +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>
>>
>> Sounds like a good idea to me
>>
>> Acked-by: David Hildenbrand <david@redhat.com>
> 
> Thanks! Am going to change this to make me and Liam M's so we can provide
> back up to Suren when he's on leave, are you fine with propagating this tag
> to this also?

Yes! Thanks

-- 
Cheers,

David / dhildenb



  reply	other threads:[~2025-04-16  8:24 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-15 13:10 [PATCH 0/2] separate out mmap_lock/VMA locking and update MAINTAINERS Lorenzo Stoakes
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 [this message]
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=a58050f9-726e-48e8-88ca-8d0d96bafb61@redhat.com \
    --to=david@redhat.com \
    --cc=Liam.Howlett@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lorenzo.stoakes@oracle.com \
    --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