get_next_ddcb(9)

✨ NAME ✨

get_next_ddcb — bestie, this is the one that grabs you the next available DDCB 💅

This page is get_next_ddcb(9) from the Kernel API Manual, and we're gonna get through it together, no cap 🫶

---

🌸 SYNOPSIS 🌸

struct ddcb * get_next_ddcb (struct genwqe_dev *cd , struct ddcb_queue
*queue , int *num );

---

🎀 ARGUMENTS 🎀

• cd — pointer to genwqe device descriptor ✨
• queue — the DDCB queue, literally the queue in question 💖
• num — internal DDCB number 🧚

---

🦋 DESCRIPTION 🦋

Okay so here's the tea: the DDCB's content is completely cleared, but there are presets for PRE and SEQNUM. That's the whole vibe 🔥

⚠️ Real talk: this function must only be called when ddcb_lock is held. Not "probably held", not "held in spirit" — held. Periodt 💀

---

👑 RETURN 👑

It returns NULL if no empty DDCB is available. Otherwise? A pointer to the next DDCB, slay ✨

---

🌈 SEE ALSO 🌈

Kernel file ./drivers/misc/genwqe/card_ddcb.c and besties:

• genwqe_crc16(9)
• ddcb_requ_finished(9)
• enqueue_ddcb(9)
• copy_ddcb_results(9)
• genwqe_check_ddcb_queue(9)
• __genwqe_wait_ddcb(9)
• __genwqe_purge_ddcb(9)
• __genwqe_enqueue_ddcb(9)
• __genwqe_execute_raw_ddcb(9)
• genwqe_next_ddcb_ready(9)
• genwqe_ddcbs_in_flight(9)
• genwqe_card_thread(9)
• genwqe_setup_service_layer(9)
• queue_wake_up_all(9)
• genwqe_finish_queue(9)
• genwqe_release_service_layer(9)

---

That's the whole page, bestie — mwah 💋 This came from ./drivers/misc/genwqe, dated October 2026, and it's giving very much kernel-manual main character energy 👑🦋💜