process_one_key_value_pair(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… process_one_key_value_pair(9)

okay so bestie, welcome to the process_one_key_value_pair page from the Kernel API Manual (man section 9, we love a section 9 moment) πŸŽ€

✨ NAME ✨

process_one_key_value_pair β€” it takes exactly one little component of an optional parameter string and updates the configuration data structure for you. one (1) pair, processed. iconic behavior honestly 🫢

✨ SYNOPSIS ✨

int process_one_key_value_pair (const char *key , unsigned int value ,
       struct device_config *config );

✨ ARGUMENTS ✨

  • key β€” the optional parameter key name, aka the "which knob are we turning" part 🌸
  • value β€” the optional parameter value, aka the "turn it to this" part ⭐
  • config β€” the configuration data structure that's gonna get updated. that's the whole point, main character energy honestly πŸ‘‘

✨ DESCRIPTION ✨

so here's the vibe check πŸ’… if the value you requested is invalid, a message gets logged and -EINVAL is returned. no cap, that's a hard no from the function.

but if the key is unknown? a message still gets logged πŸ‘€ β€” but no error is returned. lowkey gentle. it just vibes on by. the difference between those two cases is literally the whole personality of this function, so don't mix them up fr fr πŸ¦‹

✨ RETURN ✨

VDO_SUCCESS or -EINVAL πŸ’– (yes, that's the entire list, we love a simple return contract)

✨ SEE ALSO ✨

Kernel file ./drivers/md/dm-vdo/dm-vdo-target.c and its whole friend group 🌈:

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), 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), 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)


and that's the whole page bestie, you ate that πŸ’…βœ¨ one last thing: this gorgeous little manpage lives over in ./drivers/md/dm-vdo and it's dated October 2026 β€” so yeah, it's giving future icon, we stan πŸ§šπŸ’œ

πŸ“¦ where this page comes from