linux-kernel - Regression found in memory stress test with stress-ng

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

Message-ID: <CAFv23QnqgTVoB-XRe5yNndRz4-Z_3y38+QpKRxQMeZ2xQTg=gw@mail.gmail.com>
Date: Thu, 20 Mar 2025 10:49:52 +0800
From: AceLan Kao <acelan.kao@...onical.com>
To: linux-block@...r.kernel.org, axboe@...nel.dk, 
	Christoph Hellwig <hch@...radead.org>, 
	"Linux-Kernel@...r. Kernel. Org" <linux-kernel@...r.kernel.org>, yangerkun@...wei.com, houtao1@...wei.com, 
	yukuai3@...wei.com, libaokun1@...wei.com, Dirk Su <dirk.su@...onical.com>
Subject: Regression found in memory stress test with stress-ng

Hi all,

We have found a regression while doing a memory stress test using
stress-ng with the following command
   sudo stress-ng --aggressive --verify --timeout 300 --mmapmany 0

This issue occurs on recent kernel versions, and we have found that
the following commit leads to the issue
   4e63aeb5d010 ("blk-wbt: don't throttle swap writes in direct reclaim")

Before reverting the commit directly, I wonder if we can identify the
issue and implement a solution quickly.
Currently, I'm unable to provide logs, as the system becomes
unresponsive during testing. If you have any idea to capture logs,
please let me know, I'm willing to help.

Best regards,
AceLan Kao.