gfs2_rename(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… gfs2_rename(9) β€” like, the whole manual, but make it make sense

okay bestie, so this is a page from the Kernel API Manual and it's about gfs2_rename β€” yes, the rename-a-file one. buckle up, it's short but it's iconic πŸŽ€


✨ NAME ✨

gfs2_rename β€” rename a file. that's it, that's the whole vibe. a file gets a new name, we all move on 🌸


πŸ¦‹ SYNOPSIS πŸ¦‹

int gfs2_rename (struct inode *odir , struct dentry *odentry , struct
inode *ndir , struct dentry *ndentry );

four arguments, one int coming back at you. no cap, that's the entire signature πŸ”₯


πŸ‘‘ ARGUMENTS πŸ‘‘

okay so every single one of these matters, don't skip:

  • odir β€” the parent directory of the old file name. like, where the file currently lives, its current home base 🏠
  • odentry β€” the old dentry of the file. the previous name's whole situation πŸ’«
  • ndir β€” the parent directory of the new file name. the destination directory, the new neighborhood πŸ—ΊοΈ
  • ndentry β€” the new dentry of the file. the fresh name, the glow-up ✨

🌈 RETURN 🌈

errno β€” that's the return value. literally just errno. it's giving "the function tells you how it went" and we respect it πŸ’…


πŸ’– SEE ALSO πŸ’–

so many friends, okay, this function is not doing it alone. kernel file ./fs/gfs2/inode.c is where the magic lives, and here's the whole group chat 🫢


and that's the page, bestie. no notes, it ate πŸ’€

sign-off time: this one's from ./fs/gfs2, dated October 2026 β€” so yeah, mark your calendar, the future is now πŸ§šπŸ’œ

πŸ“¦ where this page comes from