From: Andrew Morton <akpm@linux-foundation.org>
To: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
Cc: Suren Baghdasaryan <surenb@google.com>,
"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>, Kees Cook <kees@kernel.org>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Christian Brauner <brauner@kernel.org>, Jan Kara <jack@suse.cz>,
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: Mon, 28 Apr 2025 16:08:16 -0700 [thread overview]
Message-ID: <20250428160816.3a22676dacd34055fd2568b7@linux-foundation.org> (raw)
In-Reply-To: <80f0d0c6-0b68-47f9-ab78-0ab7f74677fc@lucifer.local>
On Mon, 28 Apr 2025 21:26:29 +0100 Lorenzo Stoakes <lorenzo.stoakes@oracle.com> wrote:
> Andrew - I typo'd /* vma_exec.h */ below in the change to mm/vma.h - would it be
> possible to correct to vma_exec.c, or would a fixpatch make life easier?
>
I did this:
--- a/mm/vma.h~mm-establish-mm-vma_execc-for-shared-exec-mm-vma-functionality-fix
+++ a/mm/vma.h
@@ -548,7 +548,7 @@ int expand_downwards(struct vm_area_stru
int __vm_munmap(unsigned long start, size_t len, bool unlock);
-/* vma_exec.h */
+/* vma_exec.c */
#ifdef CONFIG_MMU
int relocate_vma_down(struct vm_area_struct *vma, unsigned long shift);
#endif
_
next prev parent reply other threads:[~2025-04-28 23:08 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 [this message]
2025-04-29 6:59 ` Vlastimil Babka
2025-04-29 16:53 ` Kees Cook
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=20250428160816.3a22676dacd34055fd2568b7@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=Liam.Howlett@oracle.com \
--cc=brauner@kernel.org \
--cc=david@redhat.com \
--cc=jack@suse.cz \
--cc=jannh@google.com \
--cc=kees@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox