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

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

Message-ID: <bug-195561-13602-oCzTcLx6Rw@https.bugzilla.kernel.org/>
Date:   Sun, 14 May 2017 11:41:43 +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

--- Comment #32 from Mauro Rossi (issor.oruam@...il.com) ---
(In reply to Theodore Tso from comment #31)
> So I'm just curious.  Android's fix for the problem landed in October
> 2016[1].  It's now May 2017.  Why is it that so many folks are still using
> an old version of AOSP that apparently does not have this fix?   
> 
> [1]
> https://android.googlesource.com/platform/system/extras/+/
> c71eaf37486bed9163ad528f51de29dd56b34fd2

The reason is that commit is not in the Android release cycle,
it landed in master, but we're building nougat-x86 with latest
android-7.1.2_r11 tagged version.

The mentioned problem should affect 32 bit only, or is 64bit expected to be
affected too, with the explanations given in the commit message?
Mauro

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