linux-kernel - Re: [PATCH 2/2] zram: support deflate-specific params

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: <2bnnkkwhqor73ls7dvsxlt57tp2u3xf2o27opkveuqwgh3xf2j@5kzgq4eej3cw>
Date: Thu, 15 May 2025 12:19:25 +0900
From: Sergey Senozhatsky <senozhatsky@...omium.org>
To: Herbert Xu <herbert@...dor.apana.org.au>
Cc: Sergey Senozhatsky <senozhatsky@...omium.org>, 
	Zaslonko Mikhail <zaslonko@...ux.ibm.com>, Andrew Morton <akpm@...ux-foundation.org>, 
	Minchan Kim <minchan@...nel.org>, linux-kernel@...r.kernel.org, linux-mm@...ck.org, 
	Heiko Carstens <hca@...ux.ibm.com>, Ilya Leoshkevich <iii@...ux.ibm.com>
Subject: Re: [PATCH 2/2] zram: support deflate-specific params

On (25/05/15 11:17), Herbert Xu wrote:
> On Thu, May 15, 2025 at 12:14:38PM +0900, Sergey Senozhatsky wrote:
> >
> > Yeah, so in zram we can use only raw deflate (we decompress only what we
> > have compressed earlier and the data never leaves the device.)  But in case
> > of Crypto API I actually don't know, added Herbert to the Cc.
> 
> The Crypto API has only ever used the raw deflate format.

OK, so do we want to limit user-space and permit only "raw deflate"
winbits values. that is only negative ones (either explicitly or
implicitly (by negating the value before zlib API calls))?