linux-kernel - Re: [PATCH] Ext4: Uninitialized Block Groups

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

Message-Id: <20070920162208.17f96f78.akpm@linux-foundation.org>
Date:	Thu, 20 Sep 2007 16:22:08 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Avantika Mathur <mathur@...ux.vnet.ibm.com>
Cc:	linux-kernel@...r.kernel.org, linux-ext4@...r.kernel.org,
	Andreas Dilger <adilger@...sterfs.com>, cmm@...ibm.com
Subject: Re: [PATCH] Ext4: Uninitialized Block Groups

On Tue, 18 Sep 2007 17:25:31 -0700
Avantika Mathur <mathur@...ux.vnet.ibm.com> wrote:

> In pass1 of e2fsck, every inode table in the fileystem is scanned and checked, 
> regardless of whether it is in use.  This is this the most time consuming part 
> of the filesystem check.  The unintialized block group feature can greatly 
> reduce e2fsck time by eliminating checking of uninitialized inodes.  
> 
> With this feature, there is a a high water mark of used inodes for each block 
> group.  Block and inode bitmaps can be uninitialized on disk via a flag in the
> group descriptor to avoid reading or scanning them at e2fsck time.  A checksum
> of each group descriptor is used to ensure that corruption in the group
> descriptor's bit flags does not cause incorrect operation.

This needed a few fixups due to conflicts with
ext2-ext3-ext4-add-block-bitmap-validation.patch but they were pretty
straightforward.  Please check that the result is OK.


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