linux-ext4 - [Bug 219306] ext4_truncate() is being called endlessly, all the time

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 for Android: free password hash cracker in your pocket

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

Message-ID: <bug-219306-13602-I7DZxac5vn@https.bugzilla.kernel.org/>
Date: Wed, 25 Sep 2024 22:31:05 +0000
From: bugzilla-daemon@...nel.org
To: linux-ext4@...r.kernel.org
Subject: [Bug 219306] ext4_truncate() is being called endlessly, all the time

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

--- Comment #4 from Theodore Tso (tytso@....edu) ---
"Won't be called most of the time" is rather understating the case.   The
WARN_ON should never, *EVER* fire.  If it does we have a kernel bug, and if the
user has panic_on_warn set, the kernel will crash.

Also, please note that the WARN_ON would triggers when we have a inode-specific
inconsistency.   In the extremely unlikely case that the WARN_ON triggers, the
doom loop that you are worried about would only happen if (a) panic_on_warn is
disabled, and (b) the inconsistent data state happens to be the journald's log
file.  If the file system has millions of inodes, we're talking about a
probability of one in millions, even if the kernel is buggy and triggers at
all.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.