vdo_are_same_version(9)

👑 NAME 👑

vdo_are_same_version — okay so literally what this does is check whether two version numbers are the same 💅 that's it, that's the whole vibe check

✨ SYNOPSIS ✨

bool vdo_are_same_version (struct version_number version_a , struct version_number version_b );

🎀 ARGUMENTS 🎀

• version_a — the first version, bestie. one half of the comparison 🫶
• version_b — the second version. the other half. we're comparing these two, periodt 🌸

💖 RETURN 💖

Returns true if the two versions are the same. that's the whole tea ☕ no cap, that's literally it ✨

🦋 SEE ALSO 🦋

okay so this function does NOT exist in a vacuum, she's part of a whole ensemble cast, and here's the full friend group 💜 (also the kernel file ./drivers/md/dm-vdo/encodings.h, section Block map entries(9), which is giving main character energy for this whole crew):

• vdo_pack_version_number(9)
• vdo_unpack_version_number(9)
• vdo_pack_header(9)
• vdo_unpack_header(9)
• vdo_get_index_region_start(9)
• vdo_get_data_region_start(9)
• vdo_get_index_region_size(9)
• vdo_pack_recovery_journal_entry(9)
• vdo_unpack_recovery_journal_entry(9)
• vdo_is_valid_recovery_journal_sector(9)
• vdo_compute_recovery_journal_block_number(9)
• vdo_get_journal_block_sector(9)
• vdo_pack_recovery_block_header(9)
• vdo_unpack_recovery_block_header(9)
• vdo_compute_slab_count(9)
• vdo_get_saved_reference_count_size(9)
• vdo_get_slab_journal_start_block(9)
• vdo_advance_journal_point(9)
• vdo_before_journal_point(9)
• vdo_pack_journal_point(9)
• vdo_unpack_journal_point(9)
• vdo_pack_slab_journal_block_header(9)
• vdo_unpack_slab_journal_block_header(9)
• vdo_pack_slab_journal_entry(9)
• vdo_unpack_slab_journal_entry(9)
• vdo_get_slab_summary_hint_shift(9)

go read them, they ate 🔥

and that's the whole page, bestie 🧚 this lil number lives in ./drivers/md/dm-vdo and the version you're looking at is from October 2026 — screenshot it, cite it, frame it, whatever, it's iconic and it's canon 💫