v9fs_vfs_mknod(9)

📦 version 7.3.1, in nixpkgs unstable

💫 v9fs_vfs_mknod — like, the special-file maker 💫

okay so bestie, welcome to the v9fs_vfs_mknod(9) page — it lives in the Kernel API Manual, which is honestly the most main-character manual there is 🎀

🌸 NAME 🌸

v9fs_vfs_mknod — create a special file ✨

🌈 SYNOPSIS 🌈

int v9fs_vfs_mknod (struct mnt_idmap *idmap , struct inode *dir , struct
dentry *dentry , umode_t mode , dev_t rdev );

no cap, that's the whole signature — she's compact and she knows it 💅

🦋 ARGUMENTS 🦋

so here's the group chat roll call of parameters, and yes you need all of them:

  • idmap — the idmap of the mount 🫶 like, the identity mapping this mount is vibing with.
  • dir — inode destination for the new link 📍 (yes, the docs call it a "link" here — we're just reporting the facts, bestie).
  • dentry — dentry for the file 🗂️ the little directory-entry glow-up in question.
  • mode — mode for creation 🎚️ the permission/type bits it gets born with.
  • rdev — device associated with the special file 🔌 very much the point of a special file, periodt.
ngl the argument list is short but every single one is carrying its weight — don't skip any of them 💀

👑 SEE ALSO 👑

the Kernel file ./fs/9p/vfs_inode.c, plus this whole iconic friend group of functions — literally the whole 9p crew, iykyk:

and that's the whole page, bestie — go forth and mknod responsibly 🧚‍♀️

./fs/9p · October 2026 · v9fs_vfs_mknod(9) — that's the source path, the date, and the version header, all tucked into one cute little sign-off 🍓💖 slay.
📦 where this page comes from