linux-kernel - RE: [PATCH v3] zram: Fix the issue that the write

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: <tencent_ACEF6BA50BA908889B631CCED5FF1C244F05@qq.com>
Date: Wed, 19 Nov 2025 12:09:30 +0800
From: Yuwen Chen <ywen.chen@...mail.com>
To: ywen.chen@...mail.com
Cc: 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,
	senozhatsky@...omium.org
Subject: RE: [PATCH v3] zram: Fix the issue that the write - back limits might overflow

On Wed, 19 Nov 2025 12:01:57 +0800, Yuwen Chen wrote:
> + /*
> +         * When the page size is greater than 4KB, if bd_wb_limit is set to
> +         * a value that is not page - size aligned, it will cause value
> +         * wrapping. For example, when the page size is set to 16KB and
> +         * bd_wb_limit is set to 3, a single write - back operation will
> +         * cause bd_wb_limit to become -1. Even more terrifying is that
> +         * bd_wb_limit is an unsigned number.
> +         */

Sorry, I forgot to check the code format here.