linux-ext4 - [Bug 220842] dmesg flooded with ext4 backtraces when underlying USB device chokes

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <bug-220842-13602-aALAuJW0vv@https.bugzilla.kernel.org/>
Date: Sun, 07 Dec 2025 13:04:42 +0000
From: bugzilla-daemon@...nel.org
To: linux-ext4@...r.kernel.org
Subject: [Bug 220842] dmesg flooded with ext4 backtraces when underlying USB
 device chokes

https://bugzilla.kernel.org/show_bug.cgi?id=220842

--- Comment #4 from Theodore Tso (tytso@....edu) ---
Linux doesn't have a way for the block layer to let the system know that
something terrible has happened to a storage device.   So whether the cause is
an explosion in the data center, or hard drive head crashing into the spinning
magnetic platter at 10,000 RPM, or the user just simply carelessly pulling out
a USB drive, all any file system will see is a whole set of I/O errors.    It's
not always this noisy, but in this particular case, you got unlock and it
resulted in a whole series of messages to the log.

We can try to reduce the noise, but in general, if there are problems with the
underlying storage device --- fix that first.   It should be self-evident that
if there is a problem with the underlying device, (a) it shouldn't happen, and
(b) data will be 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.