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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <aCVeeWCawIETqkfG@gondor.apana.org.au>
Date: Thu, 15 May 2025 11:24:41 +0800
From: Herbert Xu <herbert@...dor.apana.org.au>
To: Sergey Senozhatsky <senozhatsky@...omium.org>
Cc: 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 Thu, May 15, 2025 at 12:19:25PM +0900, Sergey Senozhatsky wrote:
>
> 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))?

I would suggest that we stick with the zlib values, but filter
out the ones that we don't support/use currently.  If you've already
exported this to user-space then obviously you'll need to decide
on how to maintain compatibility but that should be specific to
zram.

Cheers,
-- 
Email: Herbert Xu <herbert@...dor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt