gfs2_get_link(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

okay so bestie, welcome to the gfs2_get_link page β€” it lives in the Kernel API Manual, and it's literally about following a symbolic link. yes, that kind of following. πŸ¦‹


πŸ’… NAME πŸ’…

gfs2_get_link β€” Follow a symbolic link

like, that's the whole vibe. it follows the link. it gets the link. it is the link. periodt. πŸ”₯


✨ SYNOPSIS ✨

const char * gfs2_get_link (struct dentry *dentry , struct inode *inode
, struct delayed_call *done );

the way this signature just sits there with three arguments and a const char * return... main character energy fr fr. πŸ‘‘


πŸŽ€ ARGUMENTS πŸŽ€

  • dentry β€” The dentry of the link. that's the directory entry, the whole "where does this thing even live" situation. lowkey essential. 🌸
  • inode β€” The inode of the link. the actual metadata bestie behind the dentry. iconic duo, no cap. πŸ’–
  • done β€” destructor for return value. yes ma'am, it's a struct delayed_call * and it handles the cleanup when the returned string's time is up. we love a responsible queen. 🧚

πŸ’œ DESCRIPTION πŸ’œ

This can handle symlinks of any size.

that's it. that's the description. short, sweet, and it ate. πŸ’…βœ¨ whether your symlink is tiny or it's giving enormous, gfs2_get_link is not gonna be weird about it. no size-based gatekeeping here. 🫢


🌈 RETURN 🌈

0 on success or error code.

so like β€” 0 means slay, we're good, everything worked. anything else? that's an error code, and you should probably look at it. 😭 not me hoping your return value is 0 every single time. πŸ™ˆ

ngl, this is what the page says, so this is what you get β€” 0 on success, or an error code. don't come for me, I'm just the messenger. πŸ’€

🌟 SEE ALSO 🌟

buckle up bestie, this list is LONG and honestly? every single one of these is invited to the group chat. πŸŽ€

The kernel file, which is literally where the magic happens: ./fs/gfs2/inode.c β€” and the whole squad that lives nearby: 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_rename(9), gfs2_exchange(9), gfs2_permission(9), gfs2_setattr(9), gfs2_getattr(9).


and that's the whole page, bestie!! you understood it, I'm so proud of you, we're both so smart it's actually unreal. πŸ¦‹πŸŒΈπŸ’–

this little love letter to the kernel comes courtesy of ./fs/gfs2, dated October 2026 β€” catch you in the next manpage, mwah! πŸ˜˜πŸŽ€βœ¨

πŸ“¦ where this page comes from