fscache_write(9)

📦 version 7.3.1, in nixpkgs unstable

💾 NAME 💾

fscache_write — start a write to the cache. okay bestie, this is fscache_write(9) from the Kernel API Manual, and we are gonna get you comfy with it 💖✨

✨ SYNOPSIS ✨

the whole vibe-check signature, fr fr 👑

int fscache_write (struct netfs_cache_resources *cres , loff_t start_pos
, struct iov_iter *iter , netfs_io_terminated_t term_func , void
*term_func_priv );

🎀 ARGUMENTS 🎀

  • cres — the cache resources to use 💅
  • start_pos — the beginning file offset in the cache file ✨
  • iter — the data to write, and also the length 🫶
  • term_func — the function to call upon completion 🎀
  • term_func_priv — the private data for term_func 💖

🦋 DESCRIPTION 🦋

okay so, fscache_write starts a write to the cache. cres indicates the cache object to write to, and it must be obtained by a call to fscache_begin_operation beforehand. no cap, that part matters 👀🔥

The data to be written is obtained from the iterator, iter, and that also indicates the size of the operation. start_pos is the start position in the file. literally the coordinates of the whole thing 💫

Upon termination of the operation, term_func will be called and supplied with term_func_priv plus the amount of data written, if successful, or the error code otherwise. so it gets the private data and the result — slay, that's the callback tea ☕💅

🌈 SEE ALSO 🌈

Kernel file ./include/linux/fscache.h — go peek, iykyk 👀

mwah 💋 that’s the whole page, bestie. signing off with fscache_write(9) · source/version: ./include/linux · date: October 2026 🫶🎀

📦 where this page comes from