ubifs_bad_hash(9)

✨ NAME ✨

okay so this is ubifs_bad_hash(9) from the Kernel API Manual, and it's literally the function that reports hash mismatches 💅

💅 SYNOPSIS 💅

void ubifs_bad_hash (const struct ubifs_info *c , const void *node ,
       const u8 *hash , int lnum , int offs );

🎀 ARGUMENTS 🎀

• c — the UBIFS file-system description object, aka the whole vibe of the filesystem you're looking at 🫶
• node — the node in question, the main character of this hash drama 👑
• hash — the expected hash, like the receipt of what it should be 🧾
• lnum — the LEB the node was read from, so we know exactly where it came from 📍
• offs — the offset in that LEB where the node was read from, pinpointing the exact spot 🎯

🔥 DESCRIPTION 🔥

So basically, this function reports a hash mismatch when a node has a different hash than expected. That's it. That's the whole thing. No cap.

bestie if you're seeing this function fire, something is not slaying — the hash didn't match what was expected, and this is the function that calls it out 💀

💖 SEE ALSO 💖

Kernel file ./fs/ubifs/auth.c and its whole friend group:

• __ubifs_node_calc_hash(9)
• ubifs_hash_calc_hmac(9)
• ubifs_prepare_auth_node(9)
• __ubifs_hash_get_desc(9)
• __ubifs_node_check_hash(9)
• ubifs_sb_verify_signature(9)
• ubifs_init_authentication(9)
• __ubifs_exit_authentication(9)
• ubifs_node_calc_hmac(9)
• __ubifs_node_insert_hmac(9)
• __ubifs_node_verify_hmac(9)
• ubifs_hmac_wkm(9)

and that's the whole page, bestie 🦋 source is ./fs/ubifs, dated October 2026, and it's still ubifs_bad_hash(9) — periodt 💋✨