grow_layout(9)

💅 grow_layout(9) 💅

okay so this is from the Kernel API Manual, and bestie, we are literally about to make the layout for growing a vdo. it’s giving kernel glow-up prep, no cap. ✨

🌸 NAME 🌸

grow_layout — make the layout for growing a vdo. that’s the assignment, and she understood it. 💅

✨ SYNOPSIS ✨

int grow_layout (struct vdo *vdo , block_count_t old_size ,
block_count_t new_size );

🎀 ARGUMENTS 🎀

• vdo — the vdo that is preparing to grow. main character energy fr. 👑
• old_size — the current size of the vdo. like, the before pic. 🙈
• new_size — the size the vdo will be grown to. the glow-up destination. 🦋

💖 RETURN 💖

VDO_SUCCESS or an error code. that’s the whole vibe check. ✅

🦋 SEE ALSO 🦋

Kernel file: ./drivers/md/dm-vdo/dm-vdo-target.c

and the whole bestie squad, in order:

• free_device_config(9), get_version_number(9), parse_bool(9), parse_memory(9)
• parse_slab_size(9), process_one_thread_config_spec(9), parse_one_thread_config_spec(9), parse_thread_config_string(9)
• process_one_key_value_pair(9), parse_one_key_value_pair(9), parse_key_value_pairs(9), parse_optional_arguments(9)
• handle_parse_error(9), parse_device_config(9), get_thread_id_for_phase(9), advance_phase(9)
• finish_operation_callback(9), decode_from_super_block(9), decode_vdo(9), pre_load_callback(9)
• get_bit_array_size(9), grow_bit_array(9), allocate_instance(9), check_may_grow_physical(9)
• validate_new_device_config(9), write_super_block_for_suspend(9), suspend_callback(9), was_new(9)
• requires_repair(9), get_load_type(9), load_callback(9), handle_load_error(9)
• write_super_block_for_resume(9), resume_callback(9), grow_logical_callback(9), handle_logical_growth_error(9)
• perform_grow_logical(9), copy_partition(9), grow_physical_callback(9), handle_physical_growth_error(9)
• perform_grow_physical(9), apply_new_vdo_configuration(9)

mwah 💋 — this page lives under ./drivers/md/dm-vdo and is dated October 2026. bye bestie! 🫶