ubifs_next_log_lnum(9)

🦋 ubifs_next_log_lnum(9) — the "next log LEB" bestie

okay so this is ubifs_next_log_lnum(9), a page from the Kernel API Manual, and ngl it's a tiny little helper with a big job 💅

---

✨ NAME ✨

ubifs_next_log_lnum — switch to the next log LEB. that's it. that's the whole vibe 🎀

---

🌸 SYNOPSIS 🌸

int ubifs_next_log_lnum (const struct ubifs_info *c , int lnum );

---

💖 ARGUMENTS 💖

• c — the UBIFS file-system description object 🫶 (yes, the whole file system's lil info struct, she's carrying everything)
• lnum — the current log LEB, like the one you're standing on right now

---

🔥 DESCRIPTION 🔥

so this helper function returns the log LEB number which goes next after LEB. that's the tea ☕ literally, that's what it does — you hand her a log LEB, she tells you which one comes after it ✨

---

🌈 SEE ALSO 🌈

Kernel file ./fs/ubifs/misc.h, plus the whole friend group — go say hi 👑:

• ubifs_zn_dirty(9)
• ubifs_zn_obsolete(9)
• ubifs_zn_cow(9)
• ubifs_wake_up_bgt(9)
• ubifs_tnc_find_child(9)
• ubifs_inode(9)
• ubifs_compr_present(9)
• ubifs_compr_name(9)
• ubifs_wbuf_sync(9)
• ubifs_encode_dev(9)
• ubifs_add_dirt(9)
• ubifs_return_leb(9)
• ubifs_idx_node_sz(9)
• ubifs_idx_branch(9)
• ubifs_idx_key(9)
• ubifs_tnc_lookup(9)
• ubifs_get_lprops(9)
• ubifs_release_lprops(9)

---

fr fr that's the entire page, bestie — short and iconic, no filler, we love a low-effort-high-impact queen 💀💖

anyway mwah, this came from ./fs/ubifs, dated October 2026, and it lives at ubifs_next_log_lnum(9) — go off, read the source, slay the kernel 🧚‍♀️🌷⭐