On 2011-08-10, at 9:28 PM, Yongqiang Yang wrote:
> This patch adds a function named ext4_setup_new_desc() which sets
> up a new group descriptor and whose code is sopied from ext4_group_add().
>
> The function will be used by new resize implementation.
Again, duplicating a big hunk of ext4_group_add(). Similar comments apply.
Another question is whether this new resize code is safe from crashes?
One of the original design goals of the resize code is that it would never
leave a filesystem inconsistent if it crashed in the middle.
The way that these patches are looking, it seems that they may not be safe
in this regard, and possibly leave the filesystem in an inconsistent state
if they crash in the middle. Maybe I'm missing something?
> Signed-off-by: Yongqiang Yang <xiaoqiangnk@xxxxxxxxx>
> ---
> fs/ext4/resize.c | 54 ++++++++++++++++++++++++++++++++++++++++++++++++++++++
> 1 files changed, 54 insertions(+), 0 deletions(-)
>
> diff --git a/fs/ext4/resize.c b/fs/ext4/resize.c
> index 4fcd515..6320baa 100644
> --- a/fs/ext4/resize.c
> +++ b/fs/ext4/resize.c
> @@ -777,6 +777,60 @@ out:
> return err;
> }
>
> +/*
> + * ext4_setup_new_desc() sets up group descriptors specified by @input.
> + *
> + * @handle: journal handle
> + * @sb: super block
> + */
> +static int ext4_setup_new_desc(handle_t *handle, struct super_block *sb,
> + struct ext4_new_group_data *input)
> +{
> + struct ext4_sb_info *sbi = EXT4_SB(sb);
> + ext4_group_t group;
> + struct ext4_group_desc *gdp;
> + struct buffer_head *gdb_bh;
> + int gdb_off, gdb_num, err = 0;
> +
> + group = input->group;
> +
> + gdb_off = group % EXT4_DESC_PER_BLOCK(sb);
> + gdb_num = group / EXT4_DESC_PER_BLOCK(sb);
> +
> + /*
> + * get_write_access() has been called on gdb_bh by ext4_add_new_desc().
> + */
> + gdb_bh = sbi->s_group_desc[gdb_num];
> + /* Update group descriptor block for new group */
> + gdp = (struct ext4_group_desc *)((char *)gdb_bh->b_data +
> + gdb_off * EXT4_DESC_SIZE(sb));
> +
> + memset(gdp, 0, EXT4_DESC_SIZE(sb));
> + /* LV FIXME */
> + memset(gdp, 0, EXT4_DESC_SIZE(sb));
> + ext4_block_bitmap_set(sb, gdp, input->block_bitmap); /* LV FIXME */
> + ext4_inode_bitmap_set(sb, gdp, input->inode_bitmap); /* LV FIXME */
> + ext4_inode_table_set(sb, gdp, input->inode_table); /* LV FIXME */
> + ext4_free_blks_set(sb, gdp, input->free_blocks_count);
> + ext4_free_inodes_set(sb, gdp, EXT4_INODES_PER_GROUP(sb));
> + gdp->bg_flags = cpu_to_le16(EXT4_BG_INODE_ZEROED);
> + gdp->bg_checksum = ext4_group_desc_csum(sbi, input->group, gdp);
> +
> + err = ext4_handle_dirty_metadata(handle, NULL, gdb_bh);
> + if (unlikely(err)) {
> + ext4_std_error(sb, err);
> + return err;
> + }
> +
> + /*
> + * We can allocate memory for mb_alloc based on the new group
> + * descriptor
> + */
> + err = ext4_mb_add_groupinfo(sb, group, gdp);
> +
> + return err;
> +}
> +
> /* Add group descriptor data to an existing or new group descriptor block.
> * Ensure we handle all possible error conditions _before_ we start modifying
> * the filesystem, because we cannot abort the transaction and not have it
> --
> 1.7.5.1
>
Cheers, Andreas
--
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
