vdo_pack_sla...block_header(9)

✨ NAME ✨

okay bestie, this is the vdo_pack_sla...block_header(9) page from the Kernel API Manual 💖 and the star of the show is vdo_pack_slab_journal_block_header. Its whole job? Generate the packed representation of a slab block header. That's it, that's the vibe: take the header with the values, pack the values into the packed header, serve looks. Periodt.

📦 SYNOPSIS 📦

void vdo_pack_slab_journal_block_header (const struct
slab_journal_block_header *header , struct
packed_slab_journal_block_header *packed );

It's giving void function realness — the signature is right there, no cap. Lowkey just pass it the two headers and let it do its little packing thing. 💅

🎀 ARGUMENTS 🎀

• header — the header containing the values to encode. This is the source of the values, bestie.
• packed — the header into which to pack the values. This is where the packed representation goes.

🔗 SEE ALSO 🔗

Also check the Kernel file ./drivers/md/dm-vdo/encodings.h and this whole iconic friend group of cross-refs: Block map entries(9), vdo_are_same_version(9), 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_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).

mwah 💋 this cutie lives in ./drivers/md/dm-vdo, is dated October 2026, and is literally the vdo_pack_sla...block_header(9) page. 🫶