get_file_active(9)

get_file_active(9) 💅

okay so this is get_file_active from the Kernel API Manual, and we’re gonna get you comfy with it. Bestie, this one is short but it has main character energy because it’s one of those “please don’t touch unless you know what you’re doing” functions. 🫶

---

🌸 NAME 🌸

get_file_active — try go get a reference to a file 💅

---

✨ SYNOPSIS ✨

struct file * get_file_active (struct file **f );

---

🎀 ARGUMENTS 🎀

• f — the file to get a reference on. That’s the whole argument list, bestie. No hidden extras. ✨

---

🦋 DESCRIPTION 🦋

In contrast to get_file_rcu, the pointer itself isn’t part of the reference counting. Like, that’s the whole vibe difference here. 👀

This function should rarely have to be used, and only by users who understand the implications of SLAB_TYPESAFE_BY_RCU. Try to avoid it. No cap, the manpage is literally telling you to avoid it. 😭

⚠️ This is giving “handle with care” energy. It’s not a casual little helper to sprinkle around—only reach for it if you actually understand SLAB_TYPESAFE_BY_RCU and its implications.

---

🔥 RETURN 🔥

Returns f with the reference count increased, or NULL. That’s it. Clean, iconic, slightly scary. 💀

---

🌈 SEE ALSO 🌈

• Kernel file ./fs/file.c
• __file_ref_put(9)
• fd_install(9)
• file_close_fd_locked(9)
• last_fd(9)
• sys_close_range(9)
• file_close_fd(9)
• get_file_rcu(9)
• receive_fd(9)

---

with love from ./fs, October 2026 🫶