get_next_state(9)

✨ get_next_state(9) ✨

okay so this is a page from the Kernel API Manual, bestie, and it's about one very specific little function called get_next_state. Think of it as the vibe-check function for admin state transitions 💅

---

🌸 NAME 🌸

get_next_state — figure out which state should be set after a given operation finishes, based on the operation plus the current state. that's literally it, that's the whole job 🫶

---

🦋 SYNOPSIS 🦋

const struct admin_state_code * get_next_state (const struct admin_state
*state , const struct admin_state_code *operation );

---

🎀 ARGUMENTS 🎀

• state — the current admin state. like, where we're at right now 👀
• operation — the operation that's about to be started 🔥

---

⭐ RETURN ⭐

it hands you back the state you should set once the operation completes ✨

or it returns NULL if the operation can't even be started in the current state — so like, no, bestie, wrong vibe, can't go there 😭

---

🌈 SEE ALSO 🌈

the kernel file lives at ./drivers/md/dm-vdo/admin-state.c — and here's the whole friend group, no cap:

• vdo_finish_operation(9)
• begin_operation(9)
• start_operation(9)
• check_code(9)
• assert_vdo_drain_operation(9)
• vdo_start_draining(9)
• vdo_finish_draining(9)
• vdo_finish_draining_with_result(9)
• vdo_assert_load_operation(9)
• vdo_start_loading(9)
• vdo_finish_loading(9)
• vdo_finish_loading_with_result(9)
• assert_vdo_resume_operation(9)
• vdo_start_resuming(9)
• vdo_finish_resuming(9)
• vdo_finish_resuming_with_result(9)
• vdo_resume_if_quiescent(9)
• vdo_start_operation(9)
• vdo_start_operation_with_waiter(9)

---

💀 real talk: if get_next_state gives you NULL, do not just start the operation anyway. it's telling you the transition isn't valid from where you are. respect the vibe check, bestie.

---

and that's the whole page, mwah 💋 it's from ./drivers/md/dm-vdo, dated October 2026 — iconic of them honestly, periodt 🌟💖