vdo_modify_reference_count(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… vdo_modify_reference_count(9) β€” the Kernel API Manual, bestie edition πŸŽ€

okay so welcome to the group chat, this page lives in the Kernel API Manual and it's about one very specific little function that does exactly two things, in order, no cap. Let's get into it ✨


🌸 NAME 🌸

vdo_modify_reference_count β€” Modify the reference count of a block by first making a slab journal entry and then updating the reference counter.

like, the whole personality of this function is "journal entry first, counter second" β€” that ordering is literally the point, bestie 🫢


πŸ¦‹ SYNOPSIS πŸ¦‹

void vdo_modify_reference_count (struct vdo_completion *completion ,
struct reference_updater *updater );

it's giving void β€” nothing comes back out, the whole vibe is side effects πŸ’€


✨ ARGUMENTS ✨

  • completion β€” The data_vio completion for which to add the entry. this is the completion we're doing the whole thing for, yep πŸ’–
  • updater β€” Which of the data_vio's reference updaters is being submitted. one of them, not all of them, we gotta pick πŸŽ€

πŸ‘‘ SEE ALSO πŸ‘‘

this section is not playing around, it's a whole friend group and every single one of them is invited. from the kernel file ./drivers/md/dm-vdo/slab-depot.c:

ok that's a lot of friends but we're not skipping a single one, that would be so rude πŸ™ˆ

that's the whole page, bestie β€” short and iconic πŸ’œ this was brought to you by the fine folks over at ./drivers/md/dm-vdo, dated October 2026, and honestly? they ate. periodt 🌈⭐

πŸ“¦ where this page comes from