From: bugzilla-daemon@kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 220535] ext4 __jbd2_log_wait_for_space soft lockup and CPU stuck for 134s
Date: Fri, 05 Sep 2025 12:52:31 +0000 [thread overview]
Message-ID: <bug-220535-13602-yF4ESQmOBe@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-220535-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=220535
--- Comment #3 from waxihus@gmail.com ---
We can reproduce this issue on linux-5.15.y and linux-6.4.0, and it may also be
present in the latest mainline kernel.
What specific information should be collected after the issue has been
reproduced?
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2025-09-05 12:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-04 7:58 [Bug 220535] New: ext4 __jbd2_log_wait_for_space soft lockup and CPU stuck for 134s bugzilla-daemon
2025-09-04 8:18 ` [Bug 220535] " bugzilla-daemon
2025-09-05 8:13 ` bugzilla-daemon
2025-09-05 12:52 ` bugzilla-daemon [this message]
2025-09-05 13:34 ` bugzilla-daemon
2025-09-08 13:11 ` bugzilla-daemon
2025-09-19 2:16 ` bugzilla-daemon
2025-09-19 2:34 ` bugzilla-daemon
2025-10-30 12:48 ` bugzilla-daemon
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=bug-220535-13602-yF4ESQmOBe@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-ext4@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 NNTP newsgroup(s).