Re: prevent parallel resizers and fix some error handling in resize
From: Yongqiang Yang <hidden>
Date: 2011-07-18 10:16:08
On Mon, Jul 18, 2011 at 2:16 PM, Amir Goldstein [off-list ref] wrote:
On Mon, Jul 18, 2011 at 5:52 AM, Yongqiang Yang [off-list ref] wrote:quoted
Hi, This patch series prevents parallel resizer and fixes some error handling in resize code. Besides these, some code is simplified so that the code can be used easily in new resize implementation.You should probably mention that "new resize implementation" means: let the kernel do all the resize work, gaining fast multi group resize, flex_bg layout, and uninit block groups. The new kernel resize implementation also prepares the ground for supporting resize with features like big_alloc, 64bit and exclude_bitmap. You should probably also mention that you have already completed the "new resize implementation" and that you will post it shortly ;-)
Thank you for pointing it out:-) Yongqiang.
quoted
The patches are tested by resize2fs and e2fsck -fn. [PATCH 01/12] ext4: prevent parallel resizers by atomic bit ops [PATCH 02/12] ext4: prevent a fs with errors from being resized [PATCH 03/12] ext4: prevent a fs without journal from being resized [PATCH 04/12] ext4: rename ext4_add_groupblocks() to [PATCH 05/12] ext4: let ext4_group_add_blocks return an error code [PATCH 06/12] ext4: let ext4_group_add_blocks() handle 0 blocks [PATCH 07/12] ext4: fix a typo in ext4_group_extend() [PATCH 08/12] ext4: let setup_new_group_blocks set multi-bits each [PATCH 09/12] ext4: simplify journal handling in [PATCH 10/12] ext4: remove lock_buffer in bclean() and [PATCH 11/12] ext4: simplify parameters of add_new_gdb() [PATCH 12/12] ext4: simplify parameters of reserve_backup_gdb() -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
-- Best Wishes Yongqiang Yang -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html