[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230327194800.fzqfrxfh3nfmqwgk@revolver>
Date: Mon, 27 Mar 2023 15:48:00 -0400
From: "Liam R. Howlett" <Liam.Howlett@...cle.com>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>,
maple-tree@...ts.infradead.org, linux-mm@...ck.org,
linux-kernel@...r.kernel.org, Matthew Wilcox <willy@...radead.org>,
Suren Baghdasaryan <surenb@...gle.com>
Subject: Re: [PATCH 0/8] Fix VMA tree modification under mmap read lock
* Andrew Morton <akpm@...ux-foundation.org> [230327 15:35]:
> On Mon, 27 Mar 2023 14:55:24 -0400 "Liam R. Howlett" <Liam.Howlett@...cle.com> wrote:
>
> > These patches have been in -next since next-20230301, and have received
> > intensive testing in Android as part of the RCU page fault patchset.
> > They were also sent as part of the "Per-VMA locks" v4 patch series.
> > Patches 1 to 7 are bug fixes for RCU mode of the tree and patch 8 enables
> > RCU mode for the tree.
>
> What's happening here? I assume you've decided that the first 8
> patches of the "Per-VMA locks v4" series should be fast-tracked into
> 6.3-rcX and backported? And we retain the rest of that series for
> 6.4-rc1?
Yes, they need to be backported and fast tracked to fix the issue syzbot
found.
>
> Patch [3/8] hasn't come through to me, to linux-mm or to linux-kernel.
Should arrive shortly, I received it from one of the ML.
Powered by blists - more mailing lists