linux-kernel - Re: [PATCH v7] zram: break the strict dependency from lzo

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: <X8+30biXWgNRlKRM@google.com>
Date:   Tue, 8 Dec 2020 09:28:49 -0800
From:   Minchan Kim <minchan@...nel.org>
To:     Rui Salvaterra <rsalvaterra@...il.com>,
        Andrew Morton <akpm@...ux-foundation.org>
Cc:     ngupta@...are.org, sergey.senozhatsky.work@...il.com,
        linux-block@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v7] zram: break the strict dependency from lzo

On Tue, Dec 08, 2020 at 09:26:55AM -0800, Minchan Kim wrote:
> On Mon, Dec 07, 2020 at 12:12:45PM +0000, Rui Salvaterra wrote:
> > From the beginning, the zram block device always enabled CRYPTO_LZO, since
> > lzo-rle is hardcoded as the fallback compression algorithm. As a consequence, on
> > systems where another compression algorithm is chosen (e.g. CRYPTO_ZSTD), the
> > lzo kernel module becomes unused, while still having to be built/loaded.
> > 
> > This patch removes the hardcoded lzo-rle dependency and allows the user to
> > select the default compression algorithm for zram at build time. The previous
> > behaviour is kept, as the default algorithm is still lzo-rle.
> > 
> > Suggested-by: Sergey Senozhatsky <sergey.senozhatsky.work@...il.com>
> > Suggested-by: Minchan Kim <minchan@...nel.org>
> > Signed-off-by: Rui Salvaterra <rsalvaterra@...il.com>
> Acked-by: Minchan Kim <minchan@...nel.org>

Ccing Andrew