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]

Date:   Tue, 09 May 2017 16:10:16 +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 #29 from Theodore Tso (tytso@....edu) ---
If your firewall is not letting you access git.kernel.org, please complain to
your management.

There is a mirror of the xfstests-bld git tree on github:
https://github.com/tytso/xfstests-bld

However, to access the prebuilt test appliace files, or some of the other git
repositories needed by xfstests-bld if you want to do a build from scratch of
the test appliance, you will need access to either www.kernel.org or
git.kernel.org, so you might as well deal with your firewall configuration
issues sooner rather than later.

I basically don't trust make_ext4fs at all.   There is a reason I have been
pushing the android team to use e2fsprogs.  We do have an updated e2fsprogs in
AOSP, and some of the tools so that make_ext4fs can be replaced by mke2fs plus
some helper programs are mostly in AOSP.  They are not used by default, but
rather the Android team has been cutting devices over one at a time for Android
O, instead of whole sale.  My personal suspicion is that they very paranoid
because they are used to make_ext4fs breaking at random, so they have been
doing a slow migration over because they fear similar breakages as they migrate
away from make_ext4fs, particular as it relates to building a new system.img
file and doing a factory reset from the device.   However, if all you need to
do is format an ext4 file system on an SD card, and not try to set up a system
image or something else complicated where you have to set up SELinux labels,
etc., using mke2fs should be just fine.   It's what the rest of the Linux
ecosystem use, and what we upstream developers use for all of our regression
testing and daily personal use.   

To be clear, we do ****not**** make_ext4fs; that's an Android "special" that
was originally developed when certain management/legal types had a pathological
fear of the GPLv2, and then it grew all out of control and manageability.  
Since it was done as a clean room reimplementation, by someone who was not an
ext4 expert, and then had extra ext4 features as well as SELinux spliced into
it over time, it has caused me no end of headaches over the years....   :-(

If so Linaro folks could help accelerate the move away from make_ext4fs, I
would be most grateful.

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