fallible_matches_name(9)
β¨ 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_MATCHESif it does π«Ά - returns
NAME_LESSif the name referred to byzbris less thannm - returns
NAME_GREATERif it's greater thannm - returns
NOT_ON_MEDIAif the xentry/direntry referred to byzbrdoes 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 π
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)matches_name(9)get_znode(9)tnc_next(9)tnc_prev(9)resolve_collision(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, 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
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms