nfs_request_..._list_locked(9)

📦 version 7.3.1, in nixpkgs unstable

💅 nfs_request_..._list_locked(9) 💅

okay so this is a page from the Kernel API Manual — yes, the actual kernel one, and yes, we're gonna make it make sense. bestie, this function is lowkey just a little bookkeeping gremlin and it's iconic for it 🎀

✨ NAME ✨

nfs_request_add_commit_list_locked — adds a request to a commit list. that's the whole job. that's what she does 💅

🦋 SYNOPSIS 🦋

void nfs_request_add_commit_list_locked (struct nfs_page *req , struct
       list_head *dst , struct nfs_commit_info *cinfo );

returns void, so like… she doesn't report back. girl just does the thing and leaves 🌸

🍓 ARGUMENTS 🍓

  • req — pointer to a struct nfs_page. the request in question, the main character of this call 👑
  • dst — the commit list head. this is where the request gets parked, iykyk
  • cinfo — holds the list lock and the accounting info. it's giving "carries everything in her bag" energy 👜

💖 DESCRIPTION 💖

so here's the tea ☕ this function sets the PG_CLEAN bit, and then it updates the cinfo count of how many outstanding requests still need a commit — plus the MM page stats get updated too. no cap, it's doing three little things at once and honestly? ate.

⚠️ okay this part is IMPORTANT and not a vibe you can skip: the caller must hold NFS_I(cinfo->inode)->commit_mutex, AND the nfs_page lock. that's on you, not on her. she's locked in the name for a reason, bestie 😭🙈

🌈 SEE ALSO 🌈

like a little friend group fr fr 🫶 go read them next, slay ✨

and that's the page!! sign-off time: this one lives at ./fs/nfs, it's dated October 2026, and its title is nfs_request_..._list_locked(9). mwah, go hold that commit_mutex properly bestie 💜🧚⭐

📦 where this page comes from