STRUCT LANDLOCK_SUPERBLOCK_SECURITY(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– NAME πŸ’–

okay so bestie, this is the Kernel API Manual and we are literally looking at struct landlock_superblock_security β€” it's the superblock security blob, no cap 🫢


✨ SYNOPSIS ✨

here's the whole vibe, exactly as it slays in the source:

struct landlock_superblock_security {
    atomic_long_t inode_refs;
 };

πŸŽ€ Members πŸŽ€

  • inode_refs β€” this is the count of pending inodes (ones from this superblock, iykyk) that release_inode is still in the middle of releasing. Basically a little "how many are still in flight" tally. Cf. struct super_block->s_fsnotify_inode_refs .

πŸ¦‹ Description πŸ¦‹

the whole point of this struct? it lets hook_sb_delete wait for concurrent calls to release_inode to finish 😭 no more racing ahead while stuff is still being cleaned up β€” it's giving responsible main character energy.


πŸ‘‘ SEE ALSO πŸ‘‘

go peek at these, bestie, they're all in the same little friend group πŸ’…

  • Kernel file ./security/landlock/fs.h
  • struct landlock_inode_security(9)
  • struct landlock_file_security(9)
  • resolve_path_for_trace(9)

and that's the whole page, periodt ✨ this masterpiece lives in ./security/landlock, it's dated October 2026, and it's from the Kernel API Manual β€” go off, kernel docs, you ate πŸŒΈπŸŽ€πŸ’œ

πŸ“¦ where this page comes from