fscache_caching_failed(9)

💅 fscache_caching_failed — a kernel API manual moment (section 9, bestie)

okay so picture this: you're deep in the fscache guts, section 9 of the kernel API manual, and something went wrong and the caching just… can't anymore. that's this function. it's the "hey bestie, we need to talk" of kernel calls 🫶

---

✨ NAME ✨

fscache_caching_failed — the function that reports a failure straight up stopped caching on a cookie. like, the caching is done. cancelled. no cap 💀

---

🌸 SYNOPSIS 🌸

void fscache_caching_failed (struct fscache_cookie *cookie );

that's it. that's the whole signature. one argument, void return, main character energy only 👑

---

🎀 ARGUMENTS 🎀

• cookie — the cookie that was affected 🍪 like, the one this whole failure situation happened to. it's giving "this is personal."

---

💖 DESCRIPTION 💖

so basically you're telling fscache that caching on a cookie needs to be stopped because some sort of failure happened. not a specific failure, not a named failure — just "a failure," the vibes were off, and the caching has to end 😭

⚠️ okay this is the important part, do not skip it: this function uses no locking and must only be called from the state machine. that's not a suggestion, that's the whole rule. call it from anywhere else and you're on your own, bestie 💅

---

🦋 SEE ALSO 🦋

the kernel file ./fs/netfs/fscache_cookie.c is where the magic lives, and these are the sibling functions you should also go read, fr fr:

• fscache_end_cookie_access(9)
• fscache_begin_cookie_access(9)
• fscache_cookie_lookup_negative(9)
• fscache_resume_after_invalidation(9)
• fscache_withdraw_cookie(9)

they're all in their ./fs/netfs era together and honestly? iconic little friend group 🌈

---

and that's the page!! sourced straight from ./fs/netfs, dated October 2026, with the header and footer doing their thing so you know exactly where this lore came from ⭐ ily, go read your state machine code responsibly 💜🧚