[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <Y6/+NK6gPbn2dLwx@pc636>
Date: Sat, 31 Dec 2022 10:17:40 +0100
From: Uladzislau Rezki <urezki@...il.com>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: Uladzislau Rezki <urezki@...il.com>, 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 Thu, Dec 29, 2022 at 03:17:06PM -0800, Andrew Morton wrote:
> On Thu, 29 Dec 2022 13:47:43 +0100 Uladzislau Rezki <urezki@...il.com> wrote:
>
> > [2]
> > commit 8a85ea97b35924ee39d51e00ecb3f6d07f748a36
> > Author: Uladzislau Rezki (Sony) <urezki@...il.com>
> > Date: Wed Dec 21 18:44:53 2022 +0100
> >
> > mm: vmalloc: switch to find_unlink_vmap_area() in vm_unmap_ram()
> >
> > [3]
> > commit a7c84c673c71cdfad20fe25e5d2051ed229859f7
> > Author: Uladzislau Rezki (Sony) <urezki@...il.com>
> > Date: Wed Dec 21 18:44:52 2022 +0100
> >
> > mm: vmalloc: avoid calling __find_vmap_area() twise in __vunmap()
> > <snip>
> >
> > It would be good if you could fold [2] into [3] making it as one
> > patch. The problem is that, if we leave it as it is, the bisection
> > mechanism would consider [3] as a buggy patch, because it is not
> > fully accomplished and depends on [2].
> >
> > Is that OK for you, i mean to squash on your own?
>
> I did that. I updated the "mm: vmalloc: avoid calling
> __find_vmap_area() twice in __vunmap()" accordingly, thanks.
>
At least bisection part will not detect anything wrong now.
Happy New Year and thank you!
--
Uladzislau Rezki
Powered by blists - more mailing lists