iget5_locked_rcu(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸŽ€ iget5_locked_rcu(9) πŸŽ€

okay bestie, welcome to the Kernel API Manual β€” this is the page for iget5_locked_rcu(9), and it is literally about obtaining an inode from a mounted file system. no cap. ✨


πŸ’… NAME πŸ’…

iget5_locked_rcu β€” obtain an inode from a mounted file system.


✨ SYNOPSIS ✨

struct inode * iget5_locked_rcu (struct super_block *sb , u64 hashval ,
       int (*test)(struct inode *, void *) , int (*set)(struct inode *, void *)
       , void *data );

🫢 ARGUMENTS 🫢

  • sb β€” super block of file system. the mount's whole situation, basically. πŸ’–
  • hashval β€” hash value (usually inode number) to get.
  • test β€” callback used for comparisons between inodes.
  • set β€” callback used to initialize a new struct inode.
  • data β€” opaque data pointer to pass to test and set.

🌸 DESCRIPTION 🌸

This is equivalent to iget5_locked, except the test callback must tolerate the inode not being stable, including being mid-teardown.

bestie, this is the important part: the test callback must tolerate the inode not being stable, including being mid-teardown. like, it can be actively falling apart and your callback still has to handle that energy. πŸ˜­πŸ’…

πŸ”₯ SEE ALSO πŸ”₯

Kernel file ./fs/inode.c β€” and the whole friend group is:


mwah πŸ’‹ this page came from source ./fs, dated October 2026, and it is literally the iget5_locked_rcu(9) moment. periodt. πŸ«ΆπŸŽ€πŸ¦‹

πŸ“¦ where this page comes from