gfs2_link(9)

📦 version 7.3.1, in nixpkgs unstable

okay so bestie, we're in the gfs2_link page of the Kernel API Manual and honestly? it's a little one. a lil snack. but we're gonna read it together because that's what besties do 🫶

✨ NAME ✨

gfs2_link — literally just: link to a file. that's the whole vibe. Link to a file 💅

✨ SYNOPSIS ✨

int gfs2_link (struct dentry *old_dentry , struct inode *dir , struct
dentry *dentry );

not me copying the line break exactly the way the manpage had it, i'm so real for that 😭 anyway — it takes three things and gives you back an int, periodt.

✨ ARGUMENTS ✨

  • old_dentry — the inode you wanna link. this is the main character of the operation, the thing being pointed at 👑
  • dir — the directory you're adding the link into. it's the venue, the location, the place where the new name shows up 🎀
  • dentry — the name of the link itself. the label. the nametag at the party 🏷️

✨ DESCRIPTION ✨

so what it does: it links the inode inside old_dentry into the directory dir, using the name that lives in dentry. that's it. that's the whole thing. three pointers walk into a filesystem and one link comes out ✨

like — old thing, new place, new name. slay. no cap, that's genuinely all this page says, we're not gonna pretend there's lore 🦋

✨ RETURN ✨

errno — yes, that's the entire return section. one word. iconic honestly, she said "figure it out" 💀

✨ SEE ALSO ✨

okay this is where it gets unhinged — the see-also list on this page is long and i'm obsessed with her for it. also! the kernel file it points at is ./fs/gfs2/inode.c 📁

like, twenty-five entries. she's thorough. she's giving overachiever. we respect it 🍓

lowkey a note to self: this page is short but every word of it is load-bearing, so don't go embellishing. facts only, bestie 💖

aaaand that's the page!! ./fs/gfs2 is the source, October 2026 is the date, and gfs2_link(9) is her name — mwah, love u, go link some files responsibly 🧚💜

📦 where this page comes from