gfs2_rename(9)
π 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 π«Ά
gfs2_set_iop(9)gfs2_inode_lookup(9)gfs2_lookup_by_inum(9)gfs2_lookup_meta(9)gfs2_lookupi(9)create_ok(9)gfs2_init_xattr(9)init_dinode(9)gfs2_trans_da_blks(9)gfs2_create_inode(9)gfs2_create(9)__gfs2_lookup(9)gfs2_link(9)gfs2_unlink_inode(9)gfs2_unlink(9)gfs2_symlink(9)gfs2_mkdir(9)gfs2_mknod(9)gfs2_atomic_open(9)update_moved_ino(9)gfs2_exchange(9)gfs2_get_link(9)gfs2_permission(9)gfs2_setattr(9)gfs2_getattr(9)
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
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms