linux-ext4 - Re: [PATCH] ext4: zero out small extents when writing to prealloc area.

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]

Date:	Tue, 04 Mar 2008 23:45:17 -0700
From:	Andreas Dilger <adilger@....com>
To:	Mingming Cao <cmm@...ibm.com>
Cc:	"Aneesh Kumar K.V" <aneesh.kumar@...ux.vnet.ibm.com>,
	tytso@....edu, linux-ext4@...r.kernel.org
Subject: Re: [PATCH] ext4: zero out small extents when writing to prealloc	area.

On Mar 04, 2008  16:51 -0800, Mingming Cao wrote:
> On Tue, 2008-03-04 at 18:16 +0530, Aneesh Kumar K.V wrote:
> > +	/* If extent has less than 2*EXT4_EXT_ZERO_LEN zerout directly */
> > +	if (ee_len <= 2*EXT4_EXT_ZERO_LEN) {
> 
> Hmm, here this is range is extended to 2*EXT4_EXT_ZERO_LEN? I am a
> little more biased to keep the threshold constant as EXT4_EXT_ZERO_LEN
> around all places...

I initially thoguht this also, but it makes sense.  If the extent is
<= 2x EXT4_EXT_ZERO_LEN and it is split anywhere then the resulting
parts will be < EXT4_EXT_ZERO_LEN themselves, unless split is very
close to one edge.  Even then it is better to keep a single initialized
extent instead of 3 different ones.

Cheers, Andreas
--
Andreas Dilger
Sr. Staff Engineer, Lustre Group
Sun Microsystems of Canada, Inc.

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