From: Marcin Wanat <private@marcinwanat.pl>
To: Zhaoyang Huang <huangzhaoyang@gmail.com>
Cc: Dave Chinner <david@fromorbit.com>,
Andrew Morton <akpm@linux-foundation.org>,
"zhaoyang.huang" <zhaoyang.huang@unisoc.com>,
Alex Shi <alexs@kernel.org>,
"Kirill A . Shutemov" <kirill.shutemov@linux.intel.com>,
Hugh Dickins <hughd@google.com>,
Baolin Wang <baolin.wang@linux.alibaba.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
steve.kang@unisoc.com
Subject: Re: [PATCH 1/1] mm: protect xa split stuff under lruvec->lru_lock during migration
Date: Tue, 21 May 2024 17:47:33 +0200 [thread overview]
Message-ID: <2652f0c1-acc9-4288-8bca-c95ee49aa562@marcinwanat.pl> (raw)
In-Reply-To: <CAGWkznEG78ppUXyoM2HKoo9MCOBJQaW=vSdSKDYXJj6kWH6zjA@mail.gmail.com>
On 21.05.2024 03:00, Zhaoyang Huang wrote:
> On Tue, May 21, 2024 at 8:58 AM Zhaoyang Huang <huangzhaoyang@gmail.com> wrote:
>>
>> On Tue, May 21, 2024 at 3:42 AM Marcin Wanat <private@marcinwanat.pl> wrote:
>>>
>>> On 15.04.2024 03:50, Zhaoyang Huang wrote:
>>> I have around 50 hosts handling high I/O (each with 20Gbps+ uplinks
>>> and multiple NVMe drives), running RockyLinux 8/9. The stock RHEL
>>> kernel 8/9 is NOT affected, and the long-term kernel 5.15.X is NOT affected.
>>> However, with long-term kernels 6.1.XX and 6.6.XX,
>>> (tested at least 10 different versions), this lockup always appears
>>> after 2-30 days, similar to the report in the original thread.
>>> The more load (for example, copying a lot of local files while
>>> serving 20Gbps traffic), the higher the chance that the bug will appear.
>>>
>>> I haven't been able to reproduce this during synthetic tests,
>>> but it always occurs in production on 6.1.X and 6.6.X within 2-30 days.
>>> If anyone can provide a patch, I can test it on multiple machines
>>> over the next few days.
>> Could you please try this one which could be applied on 6.6 directly. Thank you!
> URL: https://lore.kernel.org/linux-mm/20240412064353.133497-1-zhaoyang.huang@unisoc.com/
>
Unfortunately, I am unable to cleanly apply this patch against the
latest 6.6.31
next prev parent reply other threads:[~2024-05-21 15:47 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-12 6:43 zhaoyang.huang
2024-04-12 12:24 ` Matthew Wilcox
2024-04-13 7:10 ` Zhaoyang Huang
2024-04-12 21:34 ` Andrew Morton
2024-04-13 2:01 ` Zhaoyang Huang
2024-04-15 0:09 ` Dave Chinner
2024-04-15 1:50 ` Zhaoyang Huang
2024-05-20 19:42 ` Marcin Wanat
2024-05-21 0:58 ` Zhaoyang Huang
2024-05-21 1:00 ` Zhaoyang Huang
2024-05-21 15:47 ` Marcin Wanat [this message]
2024-05-22 5:37 ` Zhaoyang Huang
2024-05-22 10:13 ` Marcin Wanat
2024-05-27 8:22 ` Marcin Wanat
2024-05-27 8:53 ` Zhaoyang Huang
2024-06-14 3:31 ` Zhaoyang Huang
2024-05-30 8:48 ` Yafang Shao
2024-05-30 8:57 ` Zhaoyang Huang
2024-05-30 9:24 ` Yafang Shao
2024-05-31 6:17 ` Zhaoyang Huang
-- strict thread matches above, loose matches on Subject: below --
2023-10-03 13:48 [BUG] soft lockup in filemap_get_read_batch antal.nemes
2024-04-16 9:31 ` [PATCH 1/1] mm: protect xa split stuff under lruvec->lru_lock during migration zhaoyang.huang
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=2652f0c1-acc9-4288-8bca-c95ee49aa562@marcinwanat.pl \
--to=private@marcinwanat.pl \
--cc=akpm@linux-foundation.org \
--cc=alexs@kernel.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=david@fromorbit.com \
--cc=huangzhaoyang@gmail.com \
--cc=hughd@google.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=steve.kang@unisoc.com \
--cc=zhaoyang.huang@unisoc.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