From: Baokun Li <libaokun1@huawei.com>
To: AceLan Kao <acelan.kao@canonical.com>
Cc: <linux-block@vger.kernel.org>, <axboe@kernel.dk>,
Christoph Hellwig <hch@infradead.org>,
"Linux-Kernel@Vger. Kernel. Org" <linux-kernel@vger.kernel.org>,
<yangerkun@huawei.com>, <houtao1@huawei.com>,
<yukuai3@huawei.com>, Dirk Su <dirk.su@canonical.com>
Subject: Re: Regression found in memory stress test with stress-ng
Date: Thu, 20 Mar 2025 11:52:20 +0800 [thread overview]
Message-ID: <180d8a88-52d9-4b83-83de-0184ed7cb4a5@huawei.com> (raw)
In-Reply-To: <CAFv23QnqgTVoB-XRe5yNndRz4-Z_3y38+QpKRxQMeZ2xQTg=gw@mail.gmail.com>
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.
>
next prev parent reply other threads:[~2025-03-20 3:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-20 2:49 AceLan Kao
2025-03-20 3:52 ` Baokun Li [this message]
2025-03-20 5:23 ` Chia-Lin Kao (AceLan)
2025-03-20 6:32 ` Baokun Li
2025-03-21 7:46 ` Chia-Lin Kao (AceLan)
2025-04-02 6:56 ` AceLan Kao
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=180d8a88-52d9-4b83-83de-0184ed7cb4a5@huawei.com \
--to=libaokun1@huawei.com \
--cc=acelan.kao@canonical.com \
--cc=axboe@kernel.dk \
--cc=dirk.su@canonical.com \
--cc=hch@infradead.org \
--cc=houtao1@huawei.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yangerkun@huawei.com \
--cc=yukuai3@huawei.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®