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

On Tue, Nov 19, 2024 at 01:04:44PM +0000, Alexey Romanov wrote:
> Should I create backend_*.c file for every compression algo driver?

No.

> Okay, there aren't many of them now. But what will do, for example,
> when there will be 250 such compression drivers?

Why would there?

> 
> And also your approach doesn't allow working with loadable modules.
> For example, we may have only binary module (without sources) from
> vendor SDK that provieds a driver for data compression. 

Well, maybe just piss off instead of sneaking in hooks for your
illegal binary modules.