Re: [PATCH v2 0/9] Mitigate a vmap lock contention v2

Uladzislau Rezki
2023-09-05T16:25:55Z

On Mon, Sep 04, 2023 at 12:53:21PM -0700, Andrew Morton wrote:
> On Mon, 4 Sep 2023 16:55:38 +0200 Uladzislau Rezki <urezki@gmail.com> wrote:
>
> > It would be good if this series somehow could be tested having some runtime
> > from the people.
>
> I grabbed it. We're supposed to avoid adding new material to -next until
> after -rc1 is released, but I've cheated before ;)
>
> That (inaccessible) pdf file is awkward. Could you please send out
> a suitable [0/N] cover letter for this series, which can be incorporated
> into the git record?
>
There will be a v3 anyway where i update the cover latter. The v2 is not
adapted to recently introduced Joel's patch, which is not in linux-next
but will land soon:

<snip>
From: "Joel Fernandes (Google)" <joel@joelfernandes.org>
Subject: mm/vmalloc: add a safer version of find_vm_area() for debug
Date: Mon, 4 Sep 2023 18:08:04 +0000

It is unsafe to dump vmalloc area information when trying to do so from
some contexts. Add a safer trylock version of the same function to do a
best-effort VMA finding and use it from vmalloc_dump_obj().
<snip>

Also it might come some extra reviews and comments for v2.

Thanks!

--
Uladzislau Rezki