linux-ext4 - Re: [PATCH 0/7] ext4: cleanups and regression fixes for grow/shrink logic V3

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: <4EB1CE58.9070200@linux.vnet.ibm.com>
Date:	Wed, 02 Nov 2011 16:12:24 -0700
From:	Allison Henderson <achender@...ux.vnet.ibm.com>
To:	Dmitry Monakhov <dmonakhov@...nvz.org>
CC:	linux-ext4@...r.kernel.org, tytso@....edu
Subject: Re: [PATCH 0/7] ext4: cleanups and regression fixes for grow/shrink
 logic V3

On 10/28/2011 10:00 AM, Dmitry Monakhov wrote:
> changes from v2 (in responce to comments from tytso@)
>   - split punch_hole handler patch in to reviewable peaces.
>   - redesign error path for ext4_ext_map_blocks
>
> ##First patch is a fix for real issue
>   ext4: Restore old EOFBLOCKS flag state after error
> ##Code cleanup for shrink logic.
>   ext4: move inode indepth shrink logic to didicated function
> ##The rest are punch hole logic fixes
>   ext4: Move punch hole logic to didicated function
>   ext4: punch_hole fix extent conversion
>   ext4: Update inode's transaction id after punch_hole
>   ext4: punch hole should be restarted after transaction restart
>   ext4: update EOFBLOCK flags after punch hole

Hi Dmitry,

I went through this set, and I think it looks good.  I didnt catch 
anything that hasnt already been explained in earlier versions, and I 
think it looks cleaner now.  Thx!

Allison Henderson

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