linux-ext4 - Problems with mballoc and uninit

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-next>] [day] [month] [year] [list]

Message-ID: <47877758.1070603@bull.net>
Date:	Fri, 11 Jan 2008 15:04:08 +0100
From:	Valerie Clement <valerie.clement@...l.net>
To:	ext4 development <linux-ext4@...r.kernel.org>
Subject: Problems with mballoc and uninit_groups option

Hi,

I've got problems with mballoc when I create the ext4 filesystem with 
the "uninit_groups" option enabled.

First, I do a single test on a filesystem created without the 
"uninit_groups" option and mounted with the defaults option:
   dd if=/dev/zero of=/mnt/test/foo bs=1M count=1024

In this case, the file blocks are allocated in the groups 4, 5, 6, 7, 8, 
9, 10.

When the filesystem is created with the "uninit_groups" option enabled 
and mounted with the defaults option, I do the same dd command.

In this case, the file blocks are allocated in the groups 5, 7, 9, 25, 
27, 49, 81. It seems that the blocks could be allocated only in the 
already initialized groups.

Who knows how to fix that?

   Valérie
-
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