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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <bug-219306-13602-C1RujOPSxt@https.bugzilla.kernel.org/>
Date: Wed, 25 Sep 2024 13:36:45 +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 #3 from Max (linmaxi@...il.com) ---
You are right, the printk was causing the problem. I figured it using ftrace.
However, I can still see how this problem can arise once there is some
(necessary) printk called along the call stack of ftruncate(2). Just for
example, in the function ext4_truncate() there is this code: 

if(!(inode->i_state & (I_NEW|I_FREEING)))
   WARN_ON(!inode_is_locked(inode));

WARN_ON is essentially a printk. While it won't be called most of the times,
once it is, the discussed problem will appear again (until the assertion wont
be true atleast).

I will try to fix this.

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

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