linux-ext4 - Re: [PATCH][e2fsprogs][mke2fs] fix FLEX

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: <20080703065553.53c35979@gara>
Date:	Thu, 3 Jul 2008 06:55:53 -0500
From:	"Jose R. Santos" <jrs@...ibm.com>
To:	Celine Bourde <celine.bourde@...l.net>
Cc:	linux-ext4@...r.kernel.org, cmm@...ibm.com,
	Frédéric Bohé 
	<frederic.bohe@...l.net>,
	SOLOFO RAMANGALAHY <Solofo.Ramangalahy@...l.net>,
	Jean-Pierre Dion <jean-pierre.dion@...l.net>
Subject: Re: [PATCH][e2fsprogs][mke2fs] fix FLEX_BG offset

On Thu, 03 Jul 2008 10:21:02 +0200
Celine Bourde <celine.bourde@...l.net> wrote:

> This patch resolves the offset problem of the flex_bg
> option when you use mke2fs tool.
> 
> For example, if you type mkfs.ext4 -I256 -O flex_bg -G32 -E test_fs <device>
> and look dumpe2fs <device> result you will see an offset problem.
> 
> Group 0: (Blocks 0-32767)
> Primary superblock at 0, Group descriptors at 1-5
> Reserved GDT blocks at 6-1024
> Block bitmap at 1025 (+1025), Inode bitmap at 1058 (+1058)
> Inode table at 1090-1601 (+1090)
> 0 free blocks, 8181 free inodes, 2 directories
> Free blocks:
> Free inodes: 12-8192
> 
> Inode bitmap must start at 1025 + 32 = 1057
> In all flexbg groups, the block between the last block bitmap and the 
> first inode
> bitmap (metatdata) is not used, which introduced a hole.
> 
> This patch corrects it.
> You have to apply it on e2fsprogs (mke2fs 1.41-WIP (17-Jun-2008)) master 
> branch.
> 
> Celine Bourde.

Acked-by: Jose R. Santos <jrs@...ibm.com>

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