ext4: revert commit which was causing fs corruption after journal replays
authorTheodore Ts'o <tytso@mit.edu>
Fri, 11 Jul 2014 17:55:40 +0000 (13:55 -0400)
committerTheodore Ts'o <tytso@mit.edu>
Fri, 11 Jul 2014 17:55:40 +0000 (13:55 -0400)
commitf9ae9cf5d72b3926ca48ea60e15bdbb840f42372
treec80eaf6959f3c8cea964782a5262a71a1d6bd92f
parent5dd214248f94d430d70e9230bda72f2654ac88a8
ext4: revert commit which was causing fs corruption after journal replays

Commit 007649375f6af2 ("ext4: initialize multi-block allocator before
checking block descriptors") causes the block group descriptor's count
of the number of free blocks to become inconsistent with the number of
free blocks in the allocation bitmap.  This is a harmless form of fs
corruption, but it causes the kernel to potentially remount the file
system read-only, or to panic, depending on the file systems's error
behavior.

Thanks to Eric Whitney for his tireless work to reproduce and to find
the guilty commit.

Fixes: 007649375f6af2 ("ext4: initialize multi-block allocator before checking block descriptors"

Cc: stable@vger.kernel.org # 3.15
Reported-by: David Jander <david@protonic.nl>
Reported-by: Matteo Croce <technoboy85@gmail.com>
Tested-by: Eric Whitney <enwlinux@gmail.com>
Suggested-by: Eric Whitney <enwlinux@gmail.com>
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
fs/ext4/super.c