[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20240710195408.c14d80b73e58af6b73be6376@linux-foundation.org>
Date: Wed, 10 Jul 2024 19:54:08 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Lorenzo Stoakes <lorenzo.stoakes@...cle.com>
Cc: linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-mm@...ck.org, "Liam R . Howlett" <Liam.Howlett@...cle.com>, Vlastimil
Babka <vbabka@...e.cz>, Matthew Wilcox <willy@...radead.org>, Alexander
Viro <viro@...iv.linux.org.uk>, Christian Brauner <brauner@...nel.org>, Jan
Kara <jack@...e.cz>, Eric Biederman <ebiederm@...ssion.com>, Kees Cook
<kees@...nel.org>, Suren Baghdasaryan <surenb@...gle.com>, SeongJae Park
<sj@...nel.org>, Shuah Khan <shuah@...nel.org>, Brendan Higgins
<brendanhiggins@...gle.com>, David Gow <davidgow@...gle.com>, Rae Moar
<rmoar@...gle.com>
Subject: Re: [PATCH v2 0/7] Make core VMA operations internal and testable
On Wed, 10 Jul 2024 20:32:05 +0100 Lorenzo Stoakes <lorenzo.stoakes@...cle.com> wrote:
> On Thu, Jul 04, 2024 at 08:27:55PM GMT, Lorenzo Stoakes wrote:
> > There are a number of "core" VMA manipulation functions implemented in
> > mm/mmap.c, notably those concerning VMA merging, splitting, modifying,
> > expanding and shrinking, which logically don't belong there.
> [snip]
>
> Hi Andrew,
>
> Wondering if we're good to look at this going to mm-unstable? As this has
> had time to settle, and received R-b tags from Liam and Vlasta.
>
> It'd be good to get it in, as it's kind of inviting merge conflicts
> otherwise and be good to get some certainty as to ordering for instance
> vs. Liam's upcoming MAP_FIXED series.
>
> Also I have some further work I'd like to build on this :>)
It's really big and it's quite new and it's really late. I think it best to await the
next -rc cycle, see how much grief it all causes.
Powered by blists - more mailing lists