find_entry_...ng_next_page(9)

📦 version 7.3.1, in nixpkgs unstable

💅 find_entry_starting_next_page(9) — from the Kernel API Manual, bestie ✨

Okay so picture this: we're deep in the kernel, in ./drivers/md/dm-vdo/repair.c, and we need to find the first journal entry after a given entry that is NOT on the same block map page. That's it. That's the whole function. It's giving "next page energy" 🦋 and honestly? Iconic.

🌸 NAME 🌸

find_entry_starting_next_page — finds the first journal entry after a given entry which is not on the same block map page. No cap, that's literally the job 💅

✨ SYNOPSIS ✨

struct numbered_block_mapping * find_entry_starting_next_page (struct
repair_completion *repair , struct numbered_block_mapping *current_entry
, bool needs_sort );

Look at that signature. Three args, one pointer coming back. Gorgeous. 🎀

🫶 ARGUMENTS 🫶

  • repair — the repair completion. Yeah, the whole completion struct. She's the main character here 👑
  • current_entry — the entry we're searching from. Our starting point, our launchpad, our home base 🚀
  • needs_sort — a bool that says whether sorting is needed to proceed. Simple as that 🍓

🔥 RETURN 🔥

A pointer to the first later journal entry that lives on a different block map page 💫

…or, if there is no subsequent entry on a different block map page, a pointer to just before the journal entries. Yeah, that's the fallback. Not a NULL, not an error — just a pointer sitting right before the entries themselves. Lowkey unhinged but it's what she does 😭

🌈 SEE ALSO 🌈

All the sibling functions, aka the whole friend group 💜 — from the kernel file ./drivers/md/dm-vdo/repair.c:

Go read them. All of them. I'm not kidding. iykyk 💅

✨ that's the whole page, bestie ✨ She lives in ./drivers/md/dm-vdo, she's dated October 2026, and she's page find_entry_...ng_next_page(9) — go off, queen 👑🎀💖

📦 where this page comes from