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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <ZPbQX3hmKR9aWsCd@pc636>
Date:   Tue, 5 Sep 2023 08:53:19 +0200
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>,
        Christoph Hellwig <hch@...radead.org>,
        Matthew Wilcox <willy@...radead.org>,
        "Liam R . Howlett" <Liam.Howlett@...cle.com>,
        Dave Chinner <david@...morbit.com>,
        "Paul E . McKenney" <paulmck@...nel.org>,
        Joel Fernandes <joel@...lfernandes.org>,
        Oleksiy Avramchenko <oleksiy.avramchenko@...y.com>
Subject: Re: [PATCH v2 0/9] Mitigate a vmap lock contention v2

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@...il.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@...lfernandes.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