linux-kernel - Re: [PATCHv2 0/7] zram: introduce compressed data writeback

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] [day] [month] [year] [list]

Message-Id: <20260118183437.6b11e6c43c7701759b73d22c@linux-foundation.org>
Date: Sun, 18 Jan 2026 18:34:37 -0800
From: Andrew Morton <akpm@...ux-foundation.org>
To: Sergey Senozhatsky <senozhatsky@...omium.org>
Cc: Richard Chang <richardycc@...gle.com>, Minchan Kim <minchan@...nel.org>,
 Brian Geffon <bgeffon@...gle.com>, David Stevens <stevensd@...gle.com>,
 linux-kernel@...r.kernel.org, linux-mm@...ck.org,
 linux-block@...r.kernel.org
Subject: Re: [PATCHv2 0/7] zram: introduce compressed data writeback

On Mon,  1 Dec 2025 18:47:47 +0900 Sergey Senozhatsky <senozhatsky@...omium.org> wrote:

> As writeback becomes more common there is another shortcoming
> that needs to be addressed - compressed data writeback.  Currently
> zram does uncompressed data writeback which is not optimal due to
> potential CPU and battery wastage.  This series changes suboptimal
> uncompressed writeback to a more optimal compressed data writeback.

I'll move this series and the "zram: use u32 for entry ac_time
tracking" series into mm-stable soon, but the review coverage is thin.

It would be good to get some more reviewer input on these zram/zsmalloc
changes.  We haven't heard from Minchan for a couple of months.  Is
there someone else who can step up and help out?

Thanks.