linux-kernel - Re: [RFC PATCHv5 0/6] zram: introduce writeback bio batching

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: <45155eea-2fde-4a72-8ea1-353bc4e14a7e@linux.alibaba.com>
Date: Sun, 23 Nov 2025 09:39:21 +0800
From: Gao Xiang <hsiangkao@...ux.alibaba.com>
To: Sergey Senozhatsky <senozhatsky@...omium.org>
Cc: Yuwen Chen <ywen.chen@...mail.com>, akpm@...ux-foundation.org,
 bgeffon@...gle.com, licayy@...look.com, linux-block@...r.kernel.org,
 linux-kernel@...r.kernel.org, linux-mm@...ck.org, minchan@...nel.org,
 richardycc@...gle.com
Subject: Re: [RFC PATCHv5 0/6] zram: introduce writeback bio batching



On 2025/11/23 08:22, Sergey Senozhatsky wrote:
> On (25/11/22 20:24), Gao Xiang wrote:
>>>
>>>> zram(ext4) -> backing ext4/btrfs
>>>
>>> This is not a valid configuration, as far as I'm concerned.
>>> Unless I'm missing your point.
>>
>> Why it's not valid? zram can be used as a regular virtual
>> block device, and format with any fs, and mount the zram
>> then.
> 
> If you want to move data between two filesystems, then just
> mount both devices and cp/mv data between them.  zram is not
> going to do that for you, zram writeback is for different
> purpose.

No, I know what zram writeback is and I was definitely not
saying using zram writeback device to mount something (if
you have interest, just check out my first reply, it's
already clear.  Also you can know why loop devices need a
workqueue or a kthread since pre-v2.6 in the first place
just because of the same reason).  I want to stop here
because it's none of my business.

Thanks,
Gao Xiang