linux-kernel - Re: [PATCH] module/decompress: use vmalloc() for zstd decompression workspace

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] [day] [month] [year] [list]

Message-ID: <ZO5BhjEyITT5YvTm@bombadil.infradead.org>
Date:   Tue, 29 Aug 2023 12:05:42 -0700
From:   Luis Chamberlain <mcgrof@...nel.org>
To:     Andrea Righi <andrea.righi@...onical.com>
Cc:     Lucas De Marchi <lucas.demarchi@...el.com>,
        Nick Terrell <terrelln@...com>,
        Dmitry Torokhov <dmitry.torokhov@...il.com>,
        Stephen Boyd <swboyd@...omium.org>,
        Piotr Gorski <lucjan.lucjanov@...il.com>,
        linux-modules@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] module/decompress: use vmalloc() for zstd decompression
 workspace

On Tue, Aug 29, 2023 at 07:46:35PM +0200, Andrea Righi wrote:
> On Tue, Aug 29, 2023 at 10:30:55AM -0700, Lucas De Marchi wrote:
> In conclusion I think we should be pretty safe for now by just changing
> gz and zstd.
> 
> Maybe having two separate patches is better (in case we need to revert
> just one for any reason...)?

Yes, that is why I already merged your zstd patch. If things do blow up
the collateral is smaller.

  Luis