linux-ext4 - Re: [PATCH] ext4: initialize multi-block allocator before checking block descriptors

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: <20140316023841.GA902@thunk.org>
Date:	Sat, 15 Mar 2014 22:38:41 -0400
From:	tytso@....edu
To:	Azat Khuzhin <a3at.mail@...il.com>
Cc:	"open list:EXT4 FILE SYSTEM" <linux-ext4@...r.kernel.org>
Subject: Re: [PATCH] ext4: initialize multi-block allocator before checking
 block descriptors

On Sun, Mar 16, 2014 at 03:54:34AM +0400, Azat Khuzhin wrote:
> 
> Thanks Ted, I'll take a look.
> Are you talking about xfs-tests failures?

Yes, the kernel is complaining that the file system looks corrupt.
The xfstest generic/001 is the easist one to trigger it:

generic/001 18s ...	[17:35:49][   26.793766] EXT4-fs error (device vde): ext4_mb_generate_buddy:756: group 1, 32763 clusters in bitmap, 32764 
in gd; block bitmap corrupt.
 [17:36:09] 20s
[   39.636943] EXT4-fs (vde): warning: mounting fs with errors, running e2fsck is recommended

I this was using a freshly generated file system using a 20 GiB test
partition, formatted using:

	   mke2fs -t ext4 -O bigalloc /dev/vde

Dropping the patch made the error go away.

Cheers,

					- Ted
--
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