ubifs_add_bud_to_log(9)

💖 NAME 💖

okay so bestie, welcome to ubifs_add_bud_to_log(9) — the kernel API manual page for ubifs_add_bud_to_log, and its whole thing is add a new bud to the log ✨. That's the vibe. 🫶

🌸 SYNOPSIS 🌸

int ubifs_add_bud_to_log (struct ubifs_info *c , int jhead , int lnum ,
       int offs );

🎀 ARGUMENTS 🎀

• c — the UBIFS file-system description object, aka the main-character context 💅
• jhead — the journal head that the bud belongs to
• lnum — the LEB number of the bud
• offs — the starting offset of the bud

🦋 DESCRIPTION 🦋

This function writes a reference node for the new bud LEB lnum to the log, and then adds it to the buds trees. It also makes sure the log size does not exceed the c->max_bud_bytes limit. No cap, it's doing the most to keep things in check 🔥

Returns zero in case of success, -EAGAIN if commit is required, and a negative error code in case of failure. So yeah: zero = slay, -EAGAIN = commit needed bestie, negative = something went off 😭

🌈 SEE ALSO 🌈

Kernel file ./fs/ubifs/log.c, plus these iconic little references:

• ubifs_search_bud(9)
• ubifs_get_wbuf(9)
• empty_log_bytes(9)
• ubifs_add_bud(9)
• remove_buds(9)
• ubifs_log_start_commit(9)
• ubifs_log_end_commit(9)
• ubifs_log_post_commit(9)
• struct done_ref(9)
• done_already(9)
• destroy_done_tree(9)
• add_node(9)
• ubifs_consolidate_log(9)
• dbg_check_bud_bytes(9)

Brought to you by ./fs/ubifs, dated October 2026, and yes bestie this page is literally ubifs_add_bud_to_log(9) 💅✨