linux-kernel - Re: EXT4-fs error (device dm-42): ext4_mb_generate_buddy:741: group 1904, 32254 clusters in bitmap, 32258 in gd

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: <20120605210806.GB7182@thunk.org>
Date:	Tue, 5 Jun 2012 17:08:06 -0400
From:	Ted Ts'o <tytso@....edu>
To:	Sander Eikelenboom <linux@...elenboom.it>
Cc:	Kees Cook <keescook@...omium.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	dm-devel@...hat.com, linux-ext4@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: EXT4-fs error (device dm-42): ext4_mb_generate_buddy:741:
 group 1904, 32254 clusters in bitmap, 32258 in gd

On Tue, Jun 05, 2012 at 10:41:54PM +0200, Sander Eikelenboom wrote:
> 
> > Today I've finally managed to bisect this to here:
> > [fd034a84e1ea5c8c8d159cd2089c32e792c269b0] ext4: split out ext4_free_blocks_after_init()
> 
> > If I revert all the "ext4:" patches in 3.2 up to and including that one,
> > I get normal behavior again.

This is excellent.  Thanks!  I'll take a deep look at that ocmmit to
see what might be going on.

> So somehow this only effects ext4 on DM (it's THE common factor in all reports) and fsck seems incapable of seeing the error (and thus repair it.)

What's probably happening is it's only the in-memory copy of the
bitmap which is getting corrupted, and because the file system is
getting remounted read-only, the corrupted bitmap is not getting
written back to disk.  (This is the whole point of remount-ro when fs
corruptions are detected.  :-)

Cheers,

						- Ted
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/