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]

Date:	Sun, 16 Mar 2014 14:46:35 -0400
From:	tytso@....edu
To:	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 08:17:13PM +0400, a3at.mail@...il.com wrote:
> And no complaints from xfs-tests, and no errors in dmesg.
> 
> Could you give me more information about you playground?

I just reproduced the problem this way.  Starting with the ext4 dev
branch of the ext4 git tree[1], which should be commit eb3e7abb161ad5,
I applied your patch, as found in the ext4 patch queue's git tree[2],
with the name initialize-multi-block-allocator-before-checking-block-descriptors

I then ran a fairly recent version of xfstests (commit 3948694eb),
under KVM with the kernel built using the 32-bit x86 architecture,
with the KVM set up with 4 CPU's, and 2048 megs of memory.  The 20 gig
partition I used was formatted using "mke2fs -t ext4 -O bigalloc", and
I used the mount options "-o block_validity" (this enables some
additional sanity checking).

The ext4 errors showed up when running xfstests ext4/305 this time
around.  Please see the attached compressed log file.

Cheers,

					- Ted

[1] git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git
[2] git://repo.or.cz/ext4-patch-queue.git

Download attachment "bigalloc-fail.log.gz" of type "application/octet-stream" (35861 bytes)