vdo_get_known_partition(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… vdo_get_known_partition β€” a Kernel API Manual moment

okay so first things first, bestie: we're in the Kernel API Manual, section 9, and this little icon is called vdo_get_known_partition. say it with me. it's giving "look up a partition by id." πŸŽ€


✨ NAME ✨

vdo_get_known_partition β€” get a partition by id from a validated layout. that's it, that's the whole job, and honestly? she ate. πŸ’–


🌸 SYNOPSIS 🌸

struct partition * vdo_get_known_partition (struct layout *layout , enum partition_id id );

like, you hand her a layout and an id, and she hands you back a struct partition *. simple. elegant. no cap. ✨


πŸ¦‹ ARGUMENTS πŸ¦‹

  • layout β€” the layout you're pulling the partition out of. it's the source, the main character, the one that's already been validated (iykyk πŸ‘€).
  • id β€” the id of the partition you want. enum partition_id, so it's typed and classy about it. πŸ’…

🌈 RETURN 🌈

the partition. that's the whole return value. she returns the partition. periodt. πŸ‘‘


πŸ”₯ SEE ALSO πŸ”₯

okay this list is LONG and it's lowkey iconic, so buckle up buttercup, we're going through the whole friend group πŸ’œ:

Kernel file ./drivers/md/dm-vdo/encodings.c, plus:

validate_version(9), vdo_validate_header(9), decode_volume_geometry(9), vdo_encode_volume_geometry(9), vdo_parse_geometry_block(9), vdo_compute_new_forest_pages(9), encode_recovery_journal_state_7_0(9), decode_recovery_journal_state_7_0(9), vdo_get_journal_operation_name(9), encode_slab_depot_state_2_0(9), decode_slab_depot_state_2_0(9), vdo_configure_slab_depot(9), vdo_configure_slab(9), vdo_decode_slab_journal_entry(9), allocate_partition(9), make_partition(9), vdo_initialize_layout(9), vdo_uninitialize_layout(9), vdo_get_partition(9), pack_vdo_config(9), pack_vdo_component(9), unpack_vdo_config(9), unpack_vdo_component_41_0(9), decode_vdo_component(9), vdo_validate_config(9), vdo_destroy_component_states(9), decode_components(9), vdo_decode_component_states(9), vdo_validate_component_states(9), vdo_encode_component_states(9), vdo_encode_super_block(9), vdo_decode_super_block(9), vdo_initialize_component_states(9), vdo_compute_index_blocks(9), vdo_initialize_volume_geometry(9)

like I said. the whole squad. 🫢


ngl bestie, the ONLY thing you need to remember: validated layout in, partition out, and id is what picks which partition. don't overthink it, she's not that kind of function. πŸ’€

and that's the tea! πŸ“ this one lives in ./drivers/md/dm-vdo and the page is dated October 2026 β€” so yeah, she's from the future, we stan a forward-thinking icon. see you in the next manpage, mwah πŸ’‹πŸ§šβ€β™€οΈβ­

πŸ“¦ where this page comes from