apply_block_entries(9)

📦 version 7.3.1, in nixpkgs unstable

✨ apply_block_entries(9) ✨

okay so bestie, welcome to apply_block_entries(9) — it's a kernel API manual page and it's literally the one that takes a block full of entries and slaps them onto the reference counts. that's the whole vibe. 💅

🌸 NAME 🌸

apply_block_entries — apply all the entries in a block to the reference counts. no cap, that's it, that's the job. ✨

🎀 SYNOPSIS 🎀

int apply_block_entries (struct packed_slab_journal_block *block ,
journal_entry_count_t entry_count , sequence_number_t block_number ,
struct vdo_slab *slab );

like, exactly that. character for character, don't come for me. 🫶

🦋 ARGUMENTS 🦋

  • block — a block with entries to apply. it's giving "the main character of this whole function" energy 👑
  • entry_count — the number of entries to apply. so how many of them we're doing. lowkey important.
  • block_number — the sequence number of the block. yes, it's called block_number, no, it is not the same thing as block. keep up 💀
  • slab — the slab to apply the entries to. this is where everything lands, bestie. 🍓

⭐ RETURN ⭐

VDO_SUCCESS or an error code. that's the whole menu. either slay or 😭.

ngl, always check it. VDO_SUCCESS is the goal, but error codes happen and you will want to know.

💖 SEE ALSO 💖

okay so this list is LONG long. like, genuinely iconic levels of long. every single one of these is a real reference and i'm not skipping a single one, so buckle up bestie:

like i said. iconic. ate. 🔥

that's the whole page bestie, you're so welcome 🫶✨

this little love letter came to you from ./drivers/md/dm-vdo, October 2026 edition — go forth and apply those entries 💜🎀

📦 where this page comes from