[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <180d8a88-52d9-4b83-83de-0184ed7cb4a5@huawei.com>
Date: Thu, 20 Mar 2025 11:52:20 +0800
From: Baokun Li <libaokun1@...wei.com>
To: AceLan Kao <acelan.kao@...onical.com>
CC: <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>, Dirk Su <dirk.su@...onical.com>
Subject: Re: Regression found in memory stress test with stress-ng
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.
>
Powered by blists - more mailing lists