GETDEVVP(9)

💅 GETDEVVP 💅

okay bestie, welcome to the getdevvp(9) page — it's a kernel developer's manual situation, and honestly? it's giving "small but mighty." three little functions, one job: making vnodes for devices. slay. 🎀

---

✨ NAME ✨

getdevvp, bdevvp, cdevvp — create a vnode for a device 🦋

---

🌸 SYNOPSIS 🌸

#include <sys/param.h>
#include <sys/vnode.h>

int
getdevvp(dev_t dev, struct vnode **vpp, enum vtype type);

int
bdevvp(dev_t dev, struct vnode **vpp);

int
cdevvp(dev_t dev, struct vnode **vpp);

---

💖 DESCRIPTION 💖

so the getdevvp() function is the main character here — it creates a vnode for a device of type type with a device number of dev, and hands you back a pointer to it in vpp. literally that's it, that's the vibe. ✨

🫶 its arguments are:

• dev — the device number of the desired device. like, which device you want. no cap.
• vpp — where the vnode will be returned on success. this is your output spot, bestie 💅
• type — the type of device, and it's either:
  • VBLK — for a block device, or
  • VCHR — for a character device.

---

bdevvp() and cdevvp() are lowkey just getdevvp with the third argument pre-filled — they use getdevvp internally, specifying the third argument for you. iconic of them honestly. 🌈

• bdevvp() will create a vnode for a block device, and it's used for the root file system and swap areas, among other things. very main character energy. 👑
• cdevvp() will create a vnode for a character device and it's used in console handling. also serving. 🍓

---

🔥 RETURN VALUES 🔥

all functions return 0 on success. periodt. 💯

if an error occurs, vpp will point to NULL — so like, don't go dereferencing that expecting a vnode, bestie, it's not there 😭

see getnewvnode(9) for further return values — there's more tea over there 🫖

---

👀 SEE ALSO 👀

• getnewvnode(9)
• vnode(9)

---

okay that's the whole page, you ate that 💅✨ and for the credits: this one's from Debian, dated September 20, 2025, and it's filed under GETDEVVP(9) — mwah, kisses, go read some vnode lore 🧚💜