linux-ext4 - [Bug 42723] EXT4-fs error: ext4_mb_generate

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-42723-13602-jvb4fq1O3o@https.bugzilla.kernel.org/>
Date:	Tue, 05 Aug 2014 12:38:33 +0000
From:	bugzilla-daemon@...zilla.kernel.org
To:	linux-ext4@...r.kernel.org
Subject: [Bug 42723] EXT4-fs error: ext4_mb_generate_buddy

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

--- Comment #23 from Theodore Tso <tytso@....edu> ---
Zhiyong,

The ext4_mb_generate_buddy() error message just means that there is an
inconsistency between the allocation bitmap and the allocation statistics in
the block group descriptor.   So people who just google for
"ext4_mb_generate_buddy" can often find old bugs that had similar symptoms.

The most recent bugfix in this area was caused by a backport of commit:

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

which caused errors after a replay.  It was reverted in mainline commit:

f9ae9cf5d72b39 ext4: revert commit which was causing fs corruption after
journal replays

You might want to check to see if that might be applicable for your kernel.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html