[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20221228154707.432e8900855122712f98037c@linux-foundation.org>
Date: Wed, 28 Dec 2022 15:47:07 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: Uladzislau Rezki <urezki@...il.com>
Cc: linux-mm@...ck.org, LKML <linux-kernel@...r.kernel.org>,
Baoquan He <bhe@...hat.com>,
Lorenzo Stoakes <lstoakes@...il.com>,
Matthew Wilcox <willy@...radead.org>,
Nicholas Piggin <npiggin@...il.com>,
Oleksiy Avramchenko <oleksiy.avramchenko@...y.com>,
Christoph Hellwig <hch@....de>
Subject: Re: [PATCH v3 2/3] mm: vmalloc: Switch to find_unlink_vmap_area()
in vm_unmap_ram()
On Fri, 23 Dec 2022 17:41:48 +0100 Uladzislau Rezki <urezki@...il.com> wrote:
> > Don't we also need to remove the manual unlink that was done
> > here previously? Actually it seems like that manual unlink is missing
> > after patch 1, creating a bisection hazard. So either add it there,
> > or just fold this patch into the previous one.
> >
> Right. In terms of bisection it is not so good. I think folding is the
> best.
>
> Andrew, could you please fold this patch into the:
which patch ;)
> [PATCH v3 1/3] mm: vmalloc: Avoid calling __find_vmap_area() twice in __vunmap() ?
>
> or should i send a v4 instead?
Yes please.
Powered by blists - more mailing lists