linux-ext4 - [Bug 195561] Suspicious persistent EXT4-fs error: ext4_validate_block_bitmap:395: [Proc] bg 17: block 557056: invalid block bitmap

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] [thread-next>] [day] [month] [year] [list]

Date:   Mon, 24 Apr 2017 16:50:08 +0000
From:   bugzilla-daemon@...zilla.kernel.org
To:     linux-ext4@...nel.org
Subject: [Bug 195561] Suspicious persistent EXT4-fs error:
 ext4_validate_block_bitmap:395: [Proc] bg 17: block 557056: invalid block
 bitmap

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

Andreas Dilger (adilger.kernelbugzilla@...ger.ca) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |adilger.kernelbugzilla@...g
                   |                            |er.ca

--- Comment #7 from Andreas Dilger (adilger.kernelbugzilla@...ger.ca) ---
Given that the same corruption is happening across different block devices, it
points to something other than the block device going bad.  It might be a bug
in the ext4 code, or some other kernel code that is corrupting the memory
(unlikely), or a userspace process that is clobbering this block.

It would be worthwhile to save a copy of the corrupted bitmap block for further
analysis.  It may be possible to identify what is overwriting that block by
looking at the content.

Collect "dumpe2fs -h" output for the filesystem, so we can see what features
are enabled.  Collect "dd if=/dev/sda1 of=/tmp/block.dat bs=4k count=1
skip=557056" and then dump it via "od -Ax4 -tx4 -a /tmp/block.dat".

You could also potentially add a tracepoint or run blktrace to see which
processes are writing to this block.  It should only be the jbd2 thread.

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