w_e_end_rsdata_req(9)

🦋 w_e_end_rsdata_req(9) — like, the Kernel API Manual page you actually wanna read 🦋

okay so bestie, welcome to the Kernel API Manual, and specifically to this one little callback that lives rent-free in DRBD land. It's a worker callback, it's doing resync business, and honestly? It ate. Let's get into it 💅

---

✨ NAME ✨

w_e_end_rsdata_req — the worker callback that sends a P_RS_DATA_REPLY packet back in response to a P_RS_DATA_REQUEST. Like, somebody asked for resync data, and this is the girl who answers. Periodt 🌸

---

🎀 SYNOPSIS 🎀

int w_e_end_rsdata_req (struct drbd_work *w , int cancel );

That's the whole vibe check: it takes your work object plus a cancel flag, and hands you back an int. Iconic signature, no notes 🫶

---

⭐ ARGUMENTS ⭐

• w — the work object. Like, the little work item this callback is riding in on. Your main character struct, fr fr 💖
• cancel — the connection will be closed anyways. Lowkey important: it's telling you the link is going bye-bye no matter what, so keep that in mind bestie 😭

---

👑 SEE ALSO 👑

Kernel file ./drivers/block/drbd/drbd_worker.c — that's where the magic lives, go read it 🧚

Then these absolute legends, all in the same family:

• w_e_end_data_req(9)
• w_send_dblock(9)
• w_send_read_req(9)
• drbd_pause_after(9)
• drbd_resume_next(9)
• drbd_start_resync(9)

Go follow them, they're mutuals 🔥

---

ngl this page is short but she's got range — every function name, every argument, every reference, all here. No cap 💀

---

that's the whole page bestie! mwah 🍓 this came straight outta ./drivers/block/drbd, dated October 2026 — catch you in the next manpage, ily bye 💜✨