On 2025/3/20 10:49, AceLan Kao wrote:
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.
Hi AceLan,
I cannot reproduce this issue. The above command will trigger OOM.
Have you enabled panic_on_oom? (You can check by sysctl vm.panic_on_oom).
Or are there more kernel Oops reports in dmesg?
Regards,
Baokun
Best regards,
AceLan Kao.
