linux-ext4 - [Bug 213627] New: Fail to read block descriptors data of ext4 filesystem

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]

Date:   Wed, 30 Jun 2021 18:06:52 +0000
From:   bugzilla-daemon@...zilla.kernel.org
To:     linux-ext4@...r.kernel.org
Subject: [Bug 213627] New: Fail to read block descriptors data of ext4
 filesystem

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

            Bug ID: 213627
           Summary: Fail to read block descriptors data of ext4 filesystem
           Product: File System
           Version: 2.5
    Kernel Version: 5.3.x-5.4.x
          Hardware: x86-64
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: high
          Priority: P1
         Component: ext4
          Assignee: fs_ext4@...nel-bugs.osdl.org
          Reporter: nipunasri.eerapu@...serve.com
        Regression: No

Our product takes backup of filesystems (ext2/3/4,xfs,btrfs) after taking the
snapshot of the volume. We have our own drivers for taking snapshot.

After taking snapshot, we calculate block group count and group descriptors
blocks in Block group0 (group zero). From group descriptors, we read block
bitmap and inode bitmaps.

All this was working well till 5.0.x kernels  and from 5.3.x kernels, block
bitmap and inode bitmap values are getting garbage. It doesnot happen all the
time.Everytime after reboot, it works fine.

Our driver simply bypasses read/write calls to system block driver, not sure
why data is corrupted.

Can you please help me what have been changed between 5.0.x and 5.3.x kernels
regarding ext,block driver.

We are not seeing this issue for xfs and btrfs filesystem.

We are suspecting something might have changed in ext2/3/4 and block driver in
5.3.x kernels.

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

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