[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <Y+C9qbbrYRtxHva9@MiWiFi-R3L-srv>
Date: Mon, 6 Feb 2023 16:43:21 +0800
From: Baoquan He <bhe@...hat.com>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: Stephen Brennan <stephen.s.brennan@...cle.com>,
linux-kernel@...r.kernel.org, linux-mm@...ck.org, urezki@...il.com,
lstoakes@...il.com, willy@...radead.org, hch@...radead.org,
error27@...il.com
Subject: Re: [PATCH v4 0/7] mm/vmalloc.c: allow vread() to read out
vm_map_ram areas
On 02/04/23 at 03:13pm, Andrew Morton wrote:
> On Sat, 4 Feb 2023 12:12:08 +0800 Baoquan He <bhe@...hat.com> wrote:
>
> > > So this definitely still resolves the originally reported issue. Feel
> > > free to add, if you want:
> > >
> > > Tested-by: Stephen Brennan <stephen.s.brennan@...cle.com>
> >
> > I noticed Andrew had picked this v4 into his mm tree, maybe Andrew can
> > help add this Tested-by tag.
>
> I dropped this series and am now unable to locate a fix which addressed
> the issue which Stephen hit.
Stephen wanted to read out vm_map_ram areas, that can't be done w/o this
patchset. The patch 3 solves his problem.
>
> Please send a v5?
I add Stephen's Reported-by and Tested-by in patch 3 and send v5.
Powered by blists - more mailing lists