kick_a_thread(9)

💅 kick_a_thread(9) — a Kernel API Manual moment

okay so bestie, welcome to the kick_a_thread page, straight out of the Kernel API Manual. yes, we're in kernel-land now, and it's giving main character energy fr fr 🎀

---

✨ NAME ✨

kick_a_thread — kick a background thread to start commit.

like, literally kick it. gently. it's a whole vibe. 🦋

---

🌸 SYNOPSIS 🌸

int kick_a_thread (void );

that's the whole thing. no cap, that's it. 💅

---

🧚 ARGUMENTS 🧚

• void — no arguments. none. zero. the function said "i need nothing from you" and honestly? iconic. 👑

---

💖 DESCRIPTION 💖

okay so here's the tea ☕ — this function kicks a background thread to start background commit. that's the whole job. it's a little nudge, a little "go go go" for the thread behind the scenes.

now the return values, pay attention bestie because this is the part where people get confused 😭:

• it returns -1 if a thread was kicked, or there's another reason to assume the memory will soon be freed or become freeable. yes, both of those live under the same -1, that's just how it is, don't shoot the messenger. 🙈
• if there are no dirty znodes, it returns 0. that's the "nothing to do here, we're chilling" answer. 🍓

so like, lowkey a -1 is not necessarily a bad thing here — it's the "something's happening / memory's about to free up" signal. key detail, don't forget it. ⭐

---

🔥 SEE ALSO 🔥

• Kernel file ./fs/ubifs/shrinker.c
• shrink_tnc(9)
• shrink_tnc_trees(9)

go read those if you want the full lore, iykyk 📚✨

---

and that's the page!! mwah 💋 this one came from ./fs/ubifs, dated October 2026, and it's the kick_a_thread(9) page — catch you in the next manpage bestie 🫶🌈👑