fallible_matches_name(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ fallible_matches_name(9) ✨

okay so bestie, we're in the kernel API manual and this one's a fallible_matches_name situation β€” no cap, it's literally about checking whether a dent matches a name πŸŽ€


🌸 NAME 🌸

fallible_matches_name β€” determine if a dent matches a given name. that's it. that's the whole vibe check πŸ’…


πŸ¦‹ SYNOPSIS πŸ¦‹

int fallible_matches_name (struct ubifs_info *c , struct ubifs_zbranch
*zbr , const struct fscrypt_name *nm );

πŸŽ€ ARGUMENTS πŸŽ€

  • c β€” the UBIFS file-system description object. your whole filesystem's little ID card πŸͺͺ
  • zbr β€” the zbranch of the dent. yes. that one. πŸ‘€
  • nm β€” the name to match. the name we're comparing against, the moment of truth ✨

πŸ’– DESCRIPTION πŸ’–

so this is the "fallible" version of the matches_name function, and the entire point is that it does not panic if the direntry/xentry that zbr refers to doesn't exist on the media. like, it's the chill one. the one that keeps its composure 😌

it checks whether the xentry/direntry referred to by zbranch zbr matches the name nm, and then it tells you what's up:

  • returns NAME_MATCHES if it does 🫢
  • returns NAME_LESS if the name referred to by zbr is less than nm
  • returns NAME_GREATER if it's greater than nm
  • returns NOT_ON_MEDIA if the xentry/direntry referred to by zbr does not exist on the media πŸ™ˆ

and if something outright fails? a negative error code comes back. that's the whole story, periodt πŸ’€


🌈 SEE ALSO 🌈

Kernel file ./fs/ubifs/tnc.c β€” this is the friend group, fr fr πŸ‘‘

that's the whole page bestie, go forth and match some names πŸ’œ

this lil angel lives in ./fs/ubifs and the docs stamped it October 2026 β€” iconic of them, honestly 🧚⭐

πŸ“¦ where this page comes from