From: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
To: David Hildenbrand <david@redhat.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
"Liam R . Howlett" <Liam.Howlett@oracle.com>,
Vlastimil Babka <vbabka@suse.cz>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Jann Horn <jannh@google.com>, Pedro Falcato <pfalcato@suse.de>
Subject: Re: [PATCH] MAINTAINERS: add additional mmap-related files to mmap section
Date: Tue, 17 Jun 2025 15:29:47 +0100 [thread overview]
Message-ID: <1bac2893-4013-4a33-9a78-413f1b9368f7@lucifer.local> (raw)
In-Reply-To: <f76e4f7b-1cac-4ce3-bd68-80d6c2ab5146@redhat.com>
On Mon, Jun 16, 2025 at 11:17:09PM +0200, David Hildenbrand wrote:
> On 16.06.25 22:35, Lorenzo Stoakes wrote:
> > msync and nommu are directly related to memory mapping, memfd and mincore
> > are less so but are roughly speaking operating on virtual memory mappings
> > from the point of view of the user so this seems the most appropriate place
> > for them.
> >
> > Signed-off-by: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
> > ---
> > MAINTAINERS | 6 +++++-
> > 1 file changed, 5 insertions(+), 1 deletion(-)
> >
> > diff --git a/MAINTAINERS b/MAINTAINERS
> > index 4523a6409186..a5d1ff923a62 100644
> > --- a/MAINTAINERS
> > +++ b/MAINTAINERS
> > @@ -15735,7 +15735,6 @@ F: Documentation/admin-guide/mm/
> > F: Documentation/mm/
> > F: include/linux/gfp.h
> > F: include/linux/gfp_types.h
> > -F: include/linux/memfd.h
> > F: include/linux/memory_hotplug.h
> > F: include/linux/memory-tiers.h
> > F: include/linux/mempolicy.h
> > @@ -15974,12 +15973,17 @@ 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: include/linux/memfd.h
> > F: include/trace/events/mmap.h
> > +F: mm/memfd.c
>
> This is much more shmem related than it is mapping related (I mean, there is
> almost nothing mapping related in there)?
>
> > +F: mm/mincore.c
> > F: mm/mlock.c
> > F: mm/mmap.c
> > F: mm/mprotect.c
> > F: mm/mremap.c
> > F: mm/mseal.c
> > +F: mm/msync.c
> > +F: mm/nommu.c
>
> There is a lot of mmap logic in there, correct. + a bunch of other weird
> things ... :(
:) Sounds like the kernel in general...
>
> --
> Cheers,
>
> David / dhildenb
>
prev parent reply other threads:[~2025-06-17 14:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-16 20:35 Lorenzo Stoakes
2025-06-16 20:49 ` Pedro Falcato
2025-06-16 21:04 ` Pedro Falcato
2025-06-17 5:19 ` Lorenzo Stoakes
2025-06-16 21:17 ` David Hildenbrand
2025-06-17 14:29 ` Lorenzo Stoakes [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=1bac2893-4013-4a33-9a78-413f1b9368f7@lucifer.local \
--to=lorenzo.stoakes@oracle.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=jannh@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pfalcato@suse.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox