linux-ext4 - Re: [RFC][Patch 2/2] Persistent preallocation in ext4

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 Dec 2006 18:31:03 +0300
From:	Alex Tomas <alex@...sterfs.com>
To:	"Amit K. Arora" <aarora@...ux.vnet.ibm.com>
Cc:	Andreas Dilger <adilger@...sterfs.com>, linux-ext4@...r.kernel.org,
	suparna@...ibm.com, cmm@...ibm.com, suzuki@...ibm.com,
	alex@...sterfs.com
Subject: Re: [RFC][Patch 2/2] Persistent preallocation in ext4

>>>>> Amit K Arora (AKA) writes:

 AKA> Above we can see that block numbers from 68 to 502 are each covered by
 AKA> more than one extent (besides couple of holes, which also might be part
 AKA> of the same problem).

 AKA> Note: A "u" in extent[u] donates that this extent is
 AKA> uninitialized, and thus was created as part of preallocation and noone
 AKA> has written to it. An "i" signifies that the extent is initialized.

 AKA> I am trying to solve this issue currently. Any suggestions are more than
 AKA> welcome.. :)

I'd write a simple function that check given leaf for consistency
(in this case you need to check that every subsequent extent doesn't
overlap previous one) and add this check in few points (before and
after change). this worked very well, especially if all extents fit
single block.

thanks, Alex
-
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