ubifs_tnc_remove_dh(9)
π ubifs_tnc_remove_dh(9) π
okay so bestie, welcome to the Kernel API Manual β¨ you're literally reading ubifs_tnc_remove_dh(9) and it's a whole lil function that lives in the kernel, no cap π«Ά
πΈ NAME πΈ
ubifs_tnc_remove_dh β remove an index entry for a "double hashed" node. periodt. that's the whole job π
β¨ SYNOPSIS β¨
int ubifs_tnc_remove_dh (struct ubifs_info *c , const union ubifs_key
*key , uint32_t cookie );
it returns an int, it takes three things, and yes the signature is exactly that β don't come for me, I copied it character for character π₯
π ARGUMENTS π
cβ the UBIFS file-system description object. your whole filesystem's identity, basically the main character πkeyβ key of node. it's aconst union ubifs_key *, so likeβ¦ look but don't touch πcookieβ node cookie for collision resolution. auint32_t. when two things hash to the same spot, this lil cookie is the tiebreaker π
π¦ DESCRIPTION π¦
Returns 0 on success or negative error code on failure. that's it, that's the whole vibe check π zero means slay, negative means something went sideways π
π SEE ALSO π
Kernel file ./fs/ubifs/tnc.c β literally the source, go read it, iykyk π§ and also these absolute icons:
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_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)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)
ngl this one's a short page but it ate, and it's giving "small function, big responsibilities" π don't forget the negative return codes exist, they WILL humble you π
k bye bestie, mwah π«Ά this lil moment was brought to you by the source ./fs/ubifs, dated October 2026, published in the Kernel API Manual, and yes ubifs_tnc_remove_dh(9) is the name, slay βπ
π¦ 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