deactivate_super(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ deactivate_super β€” kernel API manual energy ✨

Okay so bestie, we're in the Kernel API Manual today and the page is literally called deactivate_super(9). Come sit, this one's short and sweet πŸ’–


πŸŽ€ NAME πŸŽ€

deactivate_super β€” drop an active reference to superblock

Like, you're letting go of a reference. That's the whole vibe. πŸ¦‹


✨ SYNOPSIS ✨

void deactivate_super (struct super_block *s );

That's it. That's the whole signature. No cap. πŸ‘‘


🌸 ARGUMENTS 🌸

  • s β€” the superblock you want to deactivate. The one catching feelings. The one you're releasing. πŸ’…

πŸ’– DESCRIPTION πŸ’–

So deactivate_super is a variant of deactivate_locked_super, right β€” but with one iconic little plot twist: the superblock is not locked by the caller. Nope. Not your job. Not today. πŸ™ˆ

And here's the part that matters: if we're about to drop the final active reference, the lock will be acquired prior to that. So the locking still happens β€” it just happens on the function's terms, not yours. Main character energy fr fr. ✨

Lowkey the whole point: you don't bring a lock to this function. It handles that itself when it needs to. 🫢

🌈 SEE ALSO 🌈

Kernel file ./fs/super.c β€” and like, the whole extended friend group:


That's the page, bestie β€” go drop that reference responsibly πŸ’œ

Sign-off szn: this one lives in ./fs, dated October 2026, and it's filed under deactivate_super(9) in the Kernel API Manual. Periodt. πŸŽ€βœ¨

πŸ“¦ where this page comes from