FYI, I applied the following change to your patch to add support for
correct goal_block calculation. We may eventually want to factor this
out into its own libext2fs function, since there are other places in
libext2fs which are defaulting the goal block to 0, and it would be
good to make things consistent (and flex_bg allocation policy aware).
- Ted
diff --git a/lib/ext2fs/extent.c b/lib/ext2fs/extent.c
index b85a259..0fa2b2b 100644
--- a/lib/ext2fs/extent.c
+++ b/lib/ext2fs/extent.c
@@ -687,6 +687,7 @@ static errcode_t ext2fs_node_split(ext2_extent_handle_t handle, int flags)
blk_t new_node_pblk;
blk64_t new_node_start;
blk64_t orig_lblk;
+ blk64_t goal_blk = 0;
int orig_height;
char *block_buf = NULL;
struct ext2fs_extent extent;
@@ -732,6 +733,8 @@ static errcode_t ext2fs_node_split(ext2_extent_handle_t handle, int flags)
retval = ext2fs_extent_get(handle, EXT2_EXTENT_UP, &extent);
if (retval)
goto done;
+ goal_blk = extent.e_pblk;
+
retval = ext2fs_node_split(handle, 0);
if (retval)
goto done;
@@ -762,7 +765,6 @@ static errcode_t ext2fs_node_split(ext2_extent_handle_t handle, int flags)
tocopy, ext2fs_le16_to_cpu(eh->eh_entries),
handle->level);
- /* XXX um, can we make an empty node? */
if (!tocopy) {
dbg_printf("Nothing to copy to new block!\n");
retval = EXT2_ET_CANT_SPLIT_EXTENT;
@@ -776,8 +778,17 @@ static errcode_t ext2fs_node_split(ext2_extent_handle_t handle, int flags)
goto done;
}
- /* XXX FIXME this needs a decent goal block */
- retval = ext2fs_alloc_block(handle->fs, 0, block_buf, &new_node_pblk);
+ if (!goal_blk) {
+ dgrp_t group = ext2fs_group_of_ino(handle->fs, handle->ino);
+ __u8 log_flex = handle->fs->super->s_log_groups_per_flex;
+
+ if (log_flex)
+ group = group & ~((1 << (log_flex)) - 1);
+ goal_blk = (group * handle->fs->super->s_blocks_per_group) +
+ handle->fs->super->s_first_data_block;
+ }
+ retval = ext2fs_alloc_block(handle->fs, (blk_t) goal_blk, block_buf,
+ &new_node_pblk);
if (retval)
goto done;
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
