dibs_dev_alloc(9)

✨ dibs_dev_alloc(9) ✨

okay so this is a page from the Kernel API Manual (section 9, kernel-land bestie 💅) and it's about dibs_dev_alloc — the moment you get a whole device structure handed to you. iconic behaviour honestly.

---

🌸 NAME 🌸

dibs_dev_alloc — allocate and reference device structure 🎀

---

🦋 SYNOPSIS 🦋

struct dibs_dev * dibs_dev_alloc (void );

---

💜 ARGUMENTS 💜

• void — literally no arguments, bestie. you bring nothing, you get a device. that's the vibe. ✨

---

🌈 DESCRIPTION 🌈

so you call this and if it comes back happy, the following fields are valid on the returned thing:

• dev — valid upon successful return 💖
• lock — also valid upon successful return 💖

that's it, that's the whole description. two fields, both valid, both slaying. don't overthink it. 🫶

---

👑 NOTE 👑

listen to me very carefully bestie: once you've successfully called this function, you do NOT free the dibs dev directly. no cap. instead you give up your reference with put_device(dibs_get_dev(dibs)) and let it go the proper way. freeing it yourself is not it. 💀

---

⭐ RETURN ⭐

Pointer to dibs device structure. that's the whole return value. a pointer. to a dibs device structure. periodt. 🔥

---

🧚 SEE ALSO 🧚

• Kernel file ./include/linux/dibs.h
• dibs_register_client(9)
• dibs_unregister_client(9)
• dibs_dev_add(9)
• dibs_dev_del(9)

go read those too, iykyk 📚✨

---

and that's the page!! compiled out of ./include/linux, dated October 2026 — so yes, this manpage is from the future and it still looks this good 💅🦋 mwah, love u, go allocate responsibly 🎀