ubifs_tnc_lookup_dh(9)
π NAME π
okay bestie, this is page ubifs_tnc_lookup_dh(9) from the Kernel API Manual, and we're here to look up a "double hashed" node β¨π¦. That's the whole vibe: double hashed node, found by this function, periodt π
.
β¨ SYNOPSIS β¨
int ubifs_tnc_lookup_dh (struct ubifs_info *c , const union ubifs_key *key , void *node , uint32_t cookie );
π«Ά ARGUMENTS π«Ά
cβ the UBIFS file-system description object ποΈβ¨keyβ the node key to lookup ππnodeβ the node is returned here π, like this is where she landscookieβ the node cookie for collision resolution πͺπ₯
π¦ DESCRIPTION π¦
okay so this function looks up and reads a node which contains name hash in the key ππ. Since the hash may have collisions, there may be many nodes with the same key π β yes, a whole group chat with the same key β so we have to sequentially look to all of them until the needed one with the same cookie value is found πͺππ.
And the return tea β: this function returns zero in case of success π, -ENOENT if the node was not found π, and a negative error code in case of failure ππ₯.
π SEE ALSO π
Kernel file ./fs/ubifs/tnc.c plus the whole friend group: 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), 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). Go give them a vibe check π
ππ.
big slay sign-off from source/version ./fs/ubifs, dated October 2026, for ubifs_tnc_lookup_dh(9) ππ
β¨
π¦ 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