ubifs_tnc_lookup_nm(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ NAME ✨

okay so bestie, this page is about ubifs_tnc_lookup_nm β€” like, from the Kernel API Manual πŸ’… β€” and its whole thing is to look up a β€œhashed” node. iykyk ✨


🌸 SYNOPSIS 🌸

int ubifs_tnc_lookup_nm (struct ubifs_info *c , const union ubifs_key
*key , void *node , const struct fscrypt_name *nm );

πŸŽ€ ARGUMENTS πŸŽ€

  • c β€” the UBIFS file-system description object 🫢
  • key β€” the node key to look up πŸ”‘
  • node β€” the node is returned here, bestie πŸ“¦
  • nm β€” the node name 🌸

πŸ¦‹ DESCRIPTION πŸ¦‹

So this function looks up and reads a node that contains a name hash in the key. Because the hash may have collisions, there may be many nodes with the same key β€” so we have to sequentially look to all of them until the needed one is found. No cap.

It returns 0 in case of success, -ENOENT if the node was not found, and a negative error code in case of failure. That’s the whole vibe check πŸ’…

lowkey important: collisions are real, so it’s not just a one-and-done lookup β€” it checks them in sequence until it finds the right one ✨

πŸ’œ SEE ALSO πŸ’œ

Kernel file ./fs/ubifs/tnc.c β€” that’s the source bestie. The whole related-function squad is:


k bye bestie 🫢 β€” this iconic little page came from ./fs/ubifs, dated October 2026, and it’s literally for ubifs_tnc_lookup_nm(9) βœ¨πŸ’–

πŸ“¦ where this page comes from