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

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: <20241120031529.GD2668855@google.com>
Date: Wed, 20 Nov 2024 12:15:29 +0900
From: Sergey Senozhatsky <senozhatsky@...omium.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 0/3] zram: introduce crypto-backend api

On (24/11/19 15:27), 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.

Sorry, no, we are not adding this for a hypothetical scenario.

> For example, he can use some driver with hardware compression support.

Such as?  Pretty much all H/W compression modules (I'm aware of)
that people use with zram are out-of-tree.