linux-kernel - Re: [PATCH v1 3/3] zram: introduce crypto-api backend

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: <ZzyF7PAoII0E5Vf5@infradead.org>
Date: Tue, 19 Nov 2024 04:34:52 -0800
From: Christoph Hellwig <hch@...radead.org>
To: Alexey Romanov <avromanov@...utedevices.com>
Cc: minchan@...nel.org, senozhatsky@...omium.org, axboe@...nel.dk,
	terrelln@...com, linux-kernel@...r.kernel.org,
	linux-block@...r.kernel.org, kernel@...utedevices.com
Subject: Re: [PATCH v1 3/3] zram: introduce crypto-api backend

On Tue, Nov 19, 2024 at 03:27:13PM +0300, Alexey Romanov wrote:
> Since we use custom backend implementation, we remove the ability
> for users to use algorithms from crypto backend. This breaks
> backward compatibility, user doesn't necessarily use one of the
> algorithms from "custom" backends defined in zram folder.
> For example, he can use some driver with hardware compression support.
> 
> This patch adds opinion to enable Crypto API: add ZRAM_BACKEND_CRYPTO_API.
> Option is enabled by default, because in previously version of ZRAM
> it was possible to choose any alogirthm using Crypto API. This is
> also done for backward compatibility purposes.

Which crypto API algorithm do you care about?  You should probably
just add a backend for that instead of a double indirection.