prb_next_seq(9)

💖 prb_next_seq(9) 💖

okay so this is straight from the Kernel API Manual, bestie — we're talking about prb_next_seq, and it's lowkey iconic for readers who need to know where the next-newest sequence number is at. 🦋

---

✨ NAME ✨

prb_next_seq — Get the sequence number after the last available record. periodt. 💅

🎀 SYNOPSIS 🎀

u64 prb_next_seq (struct printk_ringbuffer *rb );

🌸 ARGUMENTS 🌸

• rb — The ringbuffer to get the sequence number from. That's the whole vibe. 🫶

🦋 DESCRIPTION 🦋

This is the public function available to readers to see what the next newest sequence number available to readers will be. Like, it's the function readers are allowed to call for that peek. 👑

It provides readers a sequence number to jump to if all currently available records should be skipped. And yes bestie, it is guaranteed that all records previous to the returned value have been finalized and are (or were) available to the reader. no cap. ✅

🌈 CONTEXT 🌈

Any context. literally any. 💀

⭐ RETURN ⭐

The sequence number of the next newest (not yet available) record for readers. that's the whole return vibe. ✨

👑 SEE ALSO 👑

• Kernel file ./kernel/printk/printk_ringbuffer.c printk_ringbuffer overview(9) — go read the overview, iykyk. 📖
• prb_reserve_in_last(9)
• prb_reserve(9)
• prb_commit(9)
• prb_final_commit(9)
• prb_next_reserve_seq(9)
• prb_read_valid(9)
• prb_read_valid_info(9)
• prb_first_valid_seq(9)
• prb_init(9)
• prb_record_text_space(9)

---

cute sign-off bestie: source/version is ./kernel/printk, date is October 2026, and the page is prb_next_seq(9). stay slay, keep your ringbuffer close, and read the docs 💖🎀🦋