linux-kernel - Re: [PATCH 0/3] mm: remove zpool

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: <20250904093325.2768507-1-vitaly.wool@konsulko.se>
Date: Thu,  4 Sep 2025 11:33:24 +0200
From: Vitaly Wool <vitaly.wool@...sulko.se>
To: hannes@...xchg.org
Cc: linux-kernel@...r.kernel.org,
	Vlastimil Babka <vbabka@...e.cz>,
	linux-mm@...ck.org,
	Andrew Morton <akpm@...ux-foundation.org>,
	Vitaly Wool <vitaly.wool@...sulko.se>
Subject: Re: [PATCH 0/3] mm: remove zpool

> With zswap using zsmalloc directly, there are no more in-tree users of
> this code. Remove it.
> 
> Signed-off-by: Johannes Weiner <hannes@...xchg.org>

Per the previous discussions, this gets a *NACK* from my side. There is
hardly anything _technical_ preventing new in-tree users of zpool API.
zpool API is neutral and well-defined, I don’t see *any* good reason for
it to be phased out.

BTW, remarkable is that you didn't bother to CC: me to this patch.

Anyway,

Nacked-by: Vitaly Wool <vitaly.wool@...sulko.se>