nfs_wb_folio_reclaim(9)

💅 nfs_wb_folio_reclaim — from the Kernel API Manual, bestie

okay so picture this: you're deep in the kernel, you've got a folio, and you need all its requests written back. That's this function. It's giving "cleanup era" and honestly? iconic. 🦋

---

✨ NAME ✨

nfs_wb_folio_reclaim — write back all the requests on one page. every single one. no stragglers. periodt. 💅

---

🌸 SYNOPSIS 🌸

int nfs_wb_folio_reclaim (struct inode *inode , struct folio *folio );

---

🎀 ARGUMENTS 🎀

• inode — pointer to page ✨ (yes, that's what it says, and I'm not gonna lie to you about it — it's a pointer to page, bestie)
• folio — pointer to folio 🫶

---

💖 DESCRIPTION 💖

So the whole vibe here is that this function assumes the folio has been locked by the caller. Like, it's not gonna check for you. It's not gonna lock it for you. It's just gonna trust that you already did that, because that's the kind of main character energy it's operating with. 👑

not me relying on you to hold the lock… lock it yourself before you call this, fr fr 🙈

---

🔥 SEE ALSO 🔥

Kernel file ./fs/nfs/write.c — and also these absolute legends:

• nfs_folio_find_head_request(9)
• nfs_wait_on_request(9)
• nfs_request_add_commit_list_locked(9)
• nfs_request_add_commit_list(9)
• nfs_request_remove_commit_list(9)
• nfs_wb_folio(9)

---

and that's the whole page, bestie 💜 — brought to you by the lovely folks over in ./fs/nfs, this October 2026 edition, and yes the header still says nfs_wb_folio_reclaim(9) and honestly? slay. 🌈⭐🎀