https://bugzilla.kernel.org/show_bug.cgi?id=219306 --- Comment #3 from Max (linmaxi@xxxxxxxxx) --- 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.
