From: bugzilla-daemon@kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 220842] dmesg flooded with ext4 backtraces when underlying USB device chokes
Date: Sun, 07 Dec 2025 11:13:44 +0000 [thread overview]
Message-ID: <bug-220842-13602-ElDC2TcU2t@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-220842-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=220842
--- Comment #3 from Deweloper (deweloper@wp.pl) ---
This message and tons of call traces overflowing dmesg buffer make me think
there is some software bug in ext4 fs driver:
<2>[ 5451.308209] EXT4-fs (sdb1): This should not happen!! Data will be lost
What should not happen?
Some invalid internal state?
Or an external event out of control of the software, like disappearing block
device, what is normal/expected?
In other words, is all of this noise just a way to say that a mounted device is
lost?
--
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-12-07 11:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-05 22:14 [Bug 220842] New: dmesg flooded with ext4 backtraces when underlying USB device chokes bugzilla-daemon
2025-12-06 13:36 ` [Bug 220842] " bugzilla-daemon
2025-12-06 16:25 ` bugzilla-daemon
2025-12-06 22:01 ` bugzilla-daemon
2025-12-07 11:13 ` bugzilla-daemon [this message]
2025-12-07 13:04 ` bugzilla-daemon
2025-12-07 13:07 ` bugzilla-daemon
2025-12-07 14:54 ` 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-220842-13602-ElDC2TcU2t@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