create_ok(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’« create_ok(9) πŸ’«

okay so bestie, welcome to the Kernel API Manual β€” yes we're in the kernel docs now, main character energy only πŸ’…. Today's episode: create_ok, a function that literally just answers the question "is it chill to make a new on-disk inode here?" πŸ¦‹


✨ NAME ✨

create_ok β€” OK to create a new on-disk inode here?

Like, that's the whole vibe check. It checks whether you're allowed to create. That's it. That's the function. πŸŽ€


🌸 SYNOPSIS 🌸

int create_ok (struct gfs2_inode *dip , const struct qstr *name ,
umode_t mode );

Look at her. Three params, one int return, zero chill. 🫢


🧚 ARGUMENTS 🧚

  • dip β€” the directory where the dinode is gonna live. Think of it as the folder you're moving into 🏠✨
  • name β€” the name of the new dinode. its whole identity, no pressure πŸ’€
  • mode β€” honestly? the manpage gives us nothing here. blank. empty. the original left it totally undescribed and I'm not about to invent lore πŸ™ˆ so: mode, with no description. iconic behaviour, honestly πŸ‘‘

πŸ”₯ RETURN πŸ”₯

errno

that's it. that's the return section. errno. slay, I guess πŸ’…


πŸ‘‘ SEE ALSO πŸ‘‘

okay this is the part where the manpage absolutely ate β€” look at this list, she's LONG, she's thorough, she's giving encyclopaedia energy πŸ“šβœ¨. First up, the kernel file herself:

  • Kernel file ./fs/gfs2/inode.c

and then, in the exact order we stan:

twenty-five cross-refs, no cap. she said "you WILL understand the whole inode lifecycle" and honestly? we love a thorough queen 🌈⭐


ngl bestie, no warnings, no bugs section, no exit-status drama on this one β€” it's a short and sweet little page. read it, love it, move on πŸ“

kisses and cross-references, this page came to you from ./fs/gfs2, dated October 2026 β€” and it's signed off as create_ok(9) because obviously πŸ’–βœ¨πŸŽ€

πŸ“¦ where this page comes from