Re: [PATCH v3 2/3] mm: vmalloc: Switch to find_unlink_vmap_area() in vm_unmap_ram()

From: Andrew Morton
Date: Thu Dec 29 2022 - 18:17:55 EST


On Thu, 29 Dec 2022 13:47:43 +0100 Uladzislau Rezki <urezki@xxxxxxxxx> wrote:

> [2]
> commit 8a85ea97b35924ee39d51e00ecb3f6d07f748a36
> Author: Uladzislau Rezki (Sony) <urezki@xxxxxxxxx>
> 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@xxxxxxxxx>
> 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.