fscache_cook...kup_negative(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… fscache_cook...kup_negative β€” from the Kernel API Manual, section 9, bestie

okay so bestie, welcome to fscache_cookie_lookup_negative β€” yes that's the full name, the header just got shy and truncated itself to fscache_cook...kup_negative(9), which is honestly giving "name too long for the terminal, not my problem" 😭. Anyway. It lives in the Kernel API Manual, section 9, and it is short, it is sweet, and it is very specific about when you're allowed to call it. Let's get into it ✨


πŸŽ€ NAME πŸŽ€

fscache_cookie_lookup_negative β€” the function that notes a negative lookup. That's it, that's the whole vibe check. πŸ’…


✨ SYNOPSIS ✨

void fscache_cookie_lookup_negative (struct fscache_cookie *cookie );

returns nothing, takes exactly one cookie, does not elaborate 🌸


πŸ“ ARGUMENTS πŸ“

  • cookie β€” the cookie that was being looked up πŸ‘€ like, the cookie. The one mid-lookup. That one.

πŸ¦‹ DESCRIPTION πŸ¦‹

So here's the tea, bestie πŸ«–: this function is you noting that some part of the metadata path in the cache doesn't exist. And once you've clocked that? You get to release any waiting readers β€” and you get to do it in the certain knowledge that there's nothing for them to actually read. No cap. They were waiting for literally nothing, poor things 😭. Free them. πŸ•ŠοΈ

⚠️ okay important important important: this function uses no locking. None. Zero. It is not out here protecting itself. It must only be called from the state machine β€” that's the whole rule, and it's not a suggestion, it's the law of this function fr fr πŸ’€

πŸ”₯ SEE ALSO πŸ”₯

Kernel file ./fs/netfs/fscache_cookie.c β€” that's where the sauce lives, go read it iykyk πŸ“–

And the whole little friend group: fscache_end_cookie_access(9), fscache_begin_cookie_access(9), fscache_resume_after_invalidation(9), fscache_caching_failed(9), fscache_withdraw_cookie(9) πŸ‘‘ they all hang out together, go say hi.


🌈 cute little sign-off 🌈

This page came to you from ./fs/netfs, dated October 2026, and it's still out here answering to the name fscache_cook...kup_negative(9) because we love a truncated icon πŸ’– k bye, go release those readers πŸŽ€πŸ«Ά

πŸ“¦ where this page comes from