linux-ext4 - Re: Unused block group, but all blocks not free?

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:	Fri, 22 May 2015 08:37:26 -0400
From:	Phil Susi <psusi@...ntu.com>
To:	Theodore Ts'o <tytso@....edu>
CC:	ext4 development <linux-ext4@...r.kernel.org>
Subject: Re: Unused block group, but all blocks not free?

On 5/21/2015 10:28 PM, Theodore Ts'o wrote:
> On Thu, May 21, 2015 at 08:08:17PM -0400, Phillip Susi wrote:
> The change was that for uninitialized block bitmaps, dumpe2fs used to
> display incorrect information (that is, it would claim all of the
> blocks were free, even though in fact that was not true).

It seems to have actually been a change on disk, since e2defrag *used* 
to count the number of free blocks assuming an uninitialized bitmap 
meant that they were all free, and get the same number reported in the 
superblock.  This was probably prior to the change you are thinking of.

IIRC, when I looked using debugfs, the block groups containing metadata 
always had their bitmaps initialized.

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