deactivate_locked_super(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… deactivate_locked_super β€” Kernel API Manual ✨

okay so bestie, we're in deactivate_locked_super(9) territory and honestly? it's giving "small function, big responsibility." stay with me 🫢


✨ NAME ✨

deactivate_locked_super β€” drop an active reference to superblock πŸŽ€


🌸 SYNOPSIS 🌸

void deactivate_locked_super (struct super_block *s );

like, that's the whole vibe. void return, one pointer in, no cap πŸ’…


πŸ¦‹ ARGUMENTS πŸ¦‹

  • s β€” the superblock you're deactivating. that's it. that's the argument. she's the main character here πŸ‘‘

πŸ”₯ DESCRIPTION πŸ”₯

So here's what happens, bestie. This function drops an active reference to the superblock, and β€” plot twist β€” it converts that into a temporary one if there are no other active references left. lowkey iconic behaviour tbh 🌈

In that case (the "no other active references left" case, iykyk), we tell the fs driver to shut it down, and then we drop the temporary reference we had just acquired. the way that it cleans up after itself?? obsessed πŸ’–

⚠️ important, don't skip this part: the caller holds an exclusive lock on the superblock β€” and that lock is released by this function. so don't go thinking you still have it afterward, because you literally don't 😭

πŸ‘‘ SEE ALSO πŸ‘‘

Kernel file ./fs/super.c β€” go read it, it ate ⭐


and that's the whole page, bestie β€” no crumbs left πŸ“ this one came from ./fs, dated October 2026, and yes the header said deactivate_locked_super(9) like three times because manpages are dramatic like that πŸ’€ slay, go touch some superblocks (carefully, and with the lock situation in mind) πŸ§šπŸ’œ

πŸ“¦ where this page comes from