smack_inode_rename(9)

📦 version 7.3.1, in nixpkgs unstable

💅 smack_inode_rename — the manual page, but make it a group chat

okay so bestie, you're looking at smack_inode_rename(9) from the Kernel API Manual, and honestly? she's a short one. Which like… slay for you, because you'll actually finish reading her. 💖

✨ NAME ✨

smack_inode_rename — the Smack security check that happens on rename 🎀

✨ SYNOPSIS ✨

int smack_inode_rename (struct inode *old_inode , struct dentry
     *old_dentry , struct inode *new_inode , struct dentry *new_dentry );

✨ ARGUMENTS ✨

  • old_inode — literally unused 🙈 she's just there for the vibes, bestie. don't worry about her.
  • old_dentry — the old object 💅 like where the thing was before you moved it.
  • new_inode — also unused 😭 two whole parameters doing absolutely nothing, and we respect their peace.
  • new_dentry — the new object ✨ where the thing is going.

✨ DESCRIPTION ✨

So here's the tea 🍵 — you need read and write access on both the old and new directories. Both. Not one, not "close enough", BOTH. no cap.

Returns 0 if access is permitted, an error code otherwise. that's it. that's the whole function. short queen behavior, we love to see it 👑🫶

✨ SEE ALSO ✨

The kernel file lives at ./security/smack/smack_lsm.c 🌸 and here's the entire extended family, fr fr — every single one, no skipping:

ngl bestie, that's a lot of siblings. but you asked, and I delivered. iykyk 🦋

that's the whole page!! mwah 💋 this little legend was served to you by ./security/smack, dated October 2026, and she goes by smack_inode_rename(9) — remember her name, she earned it 👑💜

📦 where this page comes from