matches_name(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– NAME πŸ’–

okay so bestie, this is matches_name(9) from the Kernel API Manual, and it's literally here to determine if a direntry or xattr entry matches a given name. no cap. πŸ’–


✨ SYNOPSIS ✨

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

πŸŽ€ ARGUMENTS πŸŽ€

  • c β€” UBIFS file-system description object. the whole filesystem context vibe.
  • zbr β€” zbranch of dent. yes, that exact little branch of dent.
  • nm β€” name to match. the name we're checking against, periodt.

πŸ”₯ DESCRIPTION πŸ”₯

so this function checks if the xentry/direntry referred by the zbranch zbr matches the name nm. that's the whole main character task. πŸ’…

here's the return-value tea: it returns NAME_MATCHES if it does match, NAME_LESS if the name referred by zbr is less than nm, and NAME_GREATER if it is greater than nm. and if something goes wrong? you get a negative error code. lowkey important. 😭


🌈 SEE ALSO 🌈

Kernel file ./fs/ubifs/tnc.c β€” the whole linked crowd is: insert_old_idx(9), insert_old_idx_znode(9), ins_clr_old_idx_znode(9), destroy_old_idx(9), copy_znode(9), add_idx_dirt(9), replace_znode(9), dirty_cow_znode(9), lnc_add(9), lnc_free(9), tnc_read_hashed_node(9), try_read_node(9), fallible_read_node(9), get_znode(9), tnc_next(9), tnc_prev(9), resolve_collision(9), fallible_matches_name(9), fallible_resolve_collision(9), matches_position(9), resolve_collision_directly(9), dirty_cow_bottom_up(9), ubifs_lookup_level0(9), lookup_level0_dirty(9), maybe_leb_gced(9), ubifs_tnc_locate(9), ubifs_tnc_get_bu_keys(9), read_wbuf(9), validate_data_node(9), ubifs_tnc_bulk_read(9), do_lookup_nm(9), ubifs_tnc_lookup_nm(9), ubifs_tnc_lookup_dh(9), correct_parent_keys(9), insert_zbranch(9), tnc_insert(9), ubifs_tnc_add(9), ubifs_tnc_replace(9), ubifs_tnc_add_nm(9), tnc_delete(9), ubifs_tnc_remove(9), ubifs_tnc_remove_nm(9), ubifs_tnc_remove_dh(9), key_in_range(9), ubifs_tnc_remove_range(9), ubifs_tnc_remove_ino(9), ubifs_tnc_next_ent(9), tnc_destroy_cnext(9), ubifs_tnc_close(9), left_znode(9), right_znode(9), lookup_znode(9), is_idx_node_in_tnc(9), is_leaf_node_in_tnc(9), ubifs_tnc_has_node(9), ubifs_dirty_idx_node(9), dbg_check_inode_size(9).


that's the whole page, bestie 🫢 β€” source/version: ./fs/ubifs; date: October 2026; and yes, it's still matches_name(9) πŸ’œβœ¨

πŸ“¦ where this page comes from