From: Chandan Babu R <chandanbabu@kernel.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-mm@kvack.org, linux-xfs@vger.kernel.org
Subject: Re: [BUG REPORT] writeback: soft lockup encountered on a next-20240327 kernel
Date: Thu, 28 Mar 2024 13:50:27 +0530 [thread overview]
Message-ID: <87y1a222al.fsf@debian-BULLSEYE-live-builder-AMD64> (raw)
In-Reply-To: <ZgUWptdgdBrcFZ1O@infradead.org>
On Thu, Mar 28, 2024 at 12:05:10 AM -0700, Christoph Hellwig wrote:
> On Thu, Mar 28, 2024 at 11:11:05AM +0530, Chandan Babu R wrote:
>> Hi,
>>
>> Executing fstest on XFS on a next-20240327 kernel resulted in two of my test
>> VMs getting into soft lockup state.
>
> What was the last linux-next tree that did work fine?
The last one I had tested was next-20240319. I did not encounter the the soft
lockup bug with that kernel.
Btw, I have restarted the tests with persistent journal enabled. I hope this
will help in figuring out the test which caused the soft lockup.
--
Chandan
prev parent reply other threads:[~2024-03-28 8:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-28 5:41 [BUG REPORT] writeback: soft lockup encountered on a next-20240327 kernel Chandan Babu R
2024-03-28 7:05 ` Christoph Hellwig
2024-03-28 8:20 ` Chandan Babu R [this message]
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=87y1a222al.fsf@debian-BULLSEYE-live-builder-AMD64 \
--to=chandanbabu@kernel.org \
--cc=hch@infradead.org \
--cc=linux-mm@kvack.org \
--cc=linux-xfs@vger.kernel.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).