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  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:	Wed, 19 Jun 2013 19:15:35 +0530
From:	Ashish Sangwan <>
To:	"Theodore Ts'o" <>
Cc:, ext4 development <>,
	Ashish Sangwan <>,
	Namjae Jeon <>
Subject: Re: [PATCH] ext4: optimize extent selection for block removal in case
 of hole punch

On Tue, Jun 18, 2013 at 9:10 PM, Theodore Ts'o <> wrote:
> On Fri, May 24, 2013 at 08:09:17PM +0530, wrote:
>> From: Ashish Sangwan <>
>> Both hole punch and truncate use ext4_ext_rm_leaf for removing
>> blocks. Currently we choose the last extent as the starting
>> point for removing blocks: ex = EXT_LAST_EXTENT(eh);
>> This is OK for truncate but for hole punch we can optimize the
>> extent selection as the path is already initialized.
>> We could use this information to select proper starting extent.
>> The code change in this patch will not affect truncate as for
>> truncate path[depth].p_ext will always be NULL.
>> Signed-off-by: Ashish Sangwan <>
>> Signed-off-by: Namjae Jeon <>
> Applied, thanks.
Hi Ted,

Sorry I cannot see the patch changes in ext4 dev branch.

>                                         - Ted
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to
More majordomo info at

Powered by blists - more mailing lists