validate_new_device_config(9)
π validate_new_device_config(9) β a Kernel API Manual moment β¨
okay so bestie, welcome to the validate_new_device_config page, straight out of the Kernel API Manual. she's a little function with a big job and honestly? she ate. let's get into it π
πΈ NAME πΈ
validate_new_device_config β check whether a new device config represents a valid modification to an existing config.
like, is this new config actually allowed to happen, or is it giving chaos? that's the whole vibe check. π¦
β¨ SYNOPSIS β¨
int validate_new_device_config (struct device_config *to_validate ,
struct device_config *config , bool may_grow , char **error_ptr );
yep, that's a int return, four arguments, and she's not messing around. π
π ARGUMENTS π
to_validateβ the new config we're checking. this is the main character of the operation, the one getting scrutinized πconfigβ the existing config. the baseline, the reference point, the "we were already here" energy πmay_growβ set totrueif growing the logical and physical size of the vdo is currently permitted. if it'sfalse, bestie, no growing. periodt. π±error_ptrβ a pointer to hold the reason for any error. so if something goes wrong, this is where the why lives π
π¦ RETURN π¦
VDO_SUCCESS or an error.
that's it. that's the whole mood. either we slay or we don't π
π SEE ALSO π
okay this list is long, but every single one of these is invited to the group chat:
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)grow_layout(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)
also the kernel file lives at ./drivers/md/dm-vdo/dm-vdo-target.c, so if you wanna go read the source, that's where she resides π«Ά
lowkey reminder: this is kernel code, so the details matter a lot. no cap. don't go renaming flags or assuming behavior, okay? iykyk π
and that's the page, bestie β¨ this one's from ./drivers/md/dm-vdo, dated October 2026, and it's literally called validate_new_device_config(9) β iconic, no notes π
π
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms