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-next>] [day] [month] [year] [list]
Message-ID: <bug-219306-13602@https.bugzilla.kernel.org/>
Date: Tue, 24 Sep 2024 11:38:38 +0000
From: bugzilla-daemon@...nel.org
To: linux-ext4@...r.kernel.org
Subject: [Bug 219306] New: ext4_truncate() is being called endlessly, all the
 time

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

            Bug ID: 219306
           Summary: ext4_truncate() is being called endlessly, all the
                    time
           Product: File System
           Version: 2.5
          Hardware: i386
                OS: Linux
            Status: NEW
          Severity: low
          Priority: P3
         Component: ext4
          Assignee: fs_ext4@...nel-bugs.osdl.org
          Reporter: linmaxi@...il.com
        Regression: No

At file ./linux/fs/ext4/extents.c there is this function: 
int ext4_ext_truncate(handle_t *handle, struct inode *inode) {...}
Which is being called all the time, from the moment the machine is booted.

Steps to reproduce: To witness it, just inject a simple printk at the beggining
of the function and checkout dmesg.

After some lookup, it turns out the inode that is being passed to the function
is
of the file: /var/log/journal/7c8e96117d45417e980f5fec3775d67f/system.journal.
The calling function is ext4_setattr(...) in the file ./linux/fs/ext4/inode.c.
At that function we have the following code:

                /*
                 * Call ext4_truncate() even if i_size didn't change to
                 * truncate possible preallocated blocks.
                 */
                if (attr->ia_size <= oldsize) {
                        rc = ext4_truncate(inode);
                        if (rc)
                                error = rc;
                }
Looks like this function is being called on system.journal file but without
actually having it's size changed. Although the comment appears to justify
calling the function even when the size is unchanged, it is probably unintended
that the function will be ran at such a high frequency without doing anything.

I'd like to ask for thoughts on this, and I'd be glad to fix it myself if
possible.

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

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ