From: Kees Cook <kees@kernel.org>
To: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
"Liam R . Howlett" <Liam.Howlett@oracle.com>,
Vlastimil Babka <vbabka@suse.cz>, Jann Horn <jannh@google.com>,
Pedro Falcato <pfalcato@suse.de>,
David Hildenbrand <david@redhat.com>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Christian Brauner <brauner@kernel.org>, Jan Kara <jack@suse.cz>,
Suren Baghdasaryan <surenb@google.com>,
linux-mm@kvack.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/4] mm: establish mm/vma_exec.c for shared exec/mm VMA functionality
Date: Tue, 29 Apr 2025 09:53:56 -0700 [thread overview]
Message-ID: <202504290953.70A8F99@keescook> (raw)
In-Reply-To: <91f2cee8f17d65214a9d83abb7011aa15f1ea690.1745853549.git.lorenzo.stoakes@oracle.com>
On Mon, Apr 28, 2025 at 04:28:14PM +0100, Lorenzo Stoakes wrote:
> There is functionality that overlaps the exec and memory mapping
> subsystems. While it properly belongs in mm, it is important that exec
> maintainers maintain oversight of this functionality correctly.
>
> We can establish both goals by adding a new mm/vma_exec.c file which
> contains these 'glue' functions, and have fs/exec.c import them.
>
> As a part of this change, to ensure that proper oversight is achieved, add
> the file to both the MEMORY MAPPING and EXEC & BINFMT API, ELF sections.
>
> scripts/get_maintainer.pl can correctly handle files in multiple entries
> and this neatly handles the cross-over.
>
> Signed-off-by: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
(I realize I didn't actually send tags...)
Reviewed-by: Kees Cook <kees@kernel.org>
--
Kees Cook
next prev parent reply other threads:[~2025-04-29 16:54 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-28 15:28 [PATCH v3 0/4] move all VMA allocation, freeing and duplication logic to mm Lorenzo Stoakes
2025-04-28 15:28 ` [PATCH v3 1/4] mm: establish mm/vma_exec.c for shared exec/mm VMA functionality Lorenzo Stoakes
2025-04-28 19:12 ` Liam R. Howlett
2025-04-28 20:14 ` Suren Baghdasaryan
2025-04-28 20:26 ` Lorenzo Stoakes
2025-04-28 23:08 ` Andrew Morton
2025-04-29 6:59 ` Vlastimil Babka
2025-04-29 16:53 ` Kees Cook [this message]
2025-04-29 17:22 ` David Hildenbrand
2025-04-29 17:48 ` Pedro Falcato
2025-04-28 15:28 ` [PATCH v3 2/4] mm: abstract initial stack setup to mm subsystem Lorenzo Stoakes
2025-04-28 19:12 ` Liam R. Howlett
2025-04-29 7:04 ` Vlastimil Babka
2025-04-29 16:54 ` Kees Cook
2025-04-29 17:48 ` Pedro Falcato
2025-04-28 15:28 ` [PATCH v3 3/4] mm: move dup_mmap() to mm Lorenzo Stoakes
2025-04-28 19:12 ` Liam R. Howlett
2025-04-28 23:31 ` Suren Baghdasaryan
2025-04-29 7:12 ` Vlastimil Babka
2025-04-29 16:54 ` Kees Cook
2025-04-29 17:23 ` David Hildenbrand
2025-04-28 15:28 ` [PATCH v3 4/4] mm: perform VMA allocation, freeing, duplication in mm Lorenzo Stoakes
2025-04-28 19:14 ` Liam R. Howlett
2025-04-28 20:28 ` Lorenzo Stoakes
2025-04-28 20:29 ` Lorenzo Stoakes
2025-04-29 7:22 ` Vlastimil Babka
2025-04-30 9:20 ` Lorenzo Stoakes
2025-04-30 21:42 ` Andrew Morton
2025-05-01 10:38 ` Lorenzo Stoakes
2025-04-29 15:04 ` Suren Baghdasaryan
2025-04-29 16:54 ` Kees Cook
2025-04-29 17:24 ` David Hildenbrand
2025-04-29 17:47 ` Pedro Falcato
2025-04-29 7:28 ` [PATCH v3 0/4] move all VMA allocation, freeing and duplication logic to mm Vlastimil Babka
2025-04-29 10:23 ` Lorenzo Stoakes
2025-04-29 16:55 ` Kees Cook
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=202504290953.70A8F99@keescook \
--to=kees@kernel.org \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=brauner@kernel.org \
--cc=david@redhat.com \
--cc=jack@suse.cz \
--cc=jannh@google.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=pfalcato@suse.de \
--cc=surenb@google.com \
--cc=vbabka@suse.cz \
--cc=viro@zeniv.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.