create_durable_rsp_buf(9)

💅 create_durable_rsp_buf — create durable handle context

okay so first things first, bestie: this page is from the Kernel API Manual, section 9. Yes, section 9, the kernel-API girly section. And the whole thing lives in the kernel file ./fs/smb/server/oplock.c, which, iconic. Let's get into it 🫶

---

✨ NAME ✨

create_durable_rsp_buf — create durable handle context

Like, the whole point of this function is literally making a durable handle context. That's the vibe. That's the assignment. Periodt. 💖

---

🦋 SYNOPSIS 🦋

void create_durable_rsp_buf (char *cc );

it returns void, ngl, so don't go looking for a return value, she's not giving you one. 🙈

---

🌸 ARGUMENTS 🌸

• cc — buffer to create durable context response. it's a char *, it's where the durable context response goes, and honestly? she's the main character of this man page. ✨

---

🔥 SEE ALSO 🔥

okay this is the part where the friend group shows up. all of these live in the kernel file ./fs/smb/server/oplock.c and honestly it's giving squad goals:

• alloc_opinfo(9)
• opinfo_write_to_read(9)
• opinfo_read_handle_to_read(9)
• opinfo_write_to_none(9)
• opinfo_read_to_none(9)
• lease_read_to_write(9)
• lease_none_upgrade(9)
• close_id_del_oplock(9)
• grant_write_oplock(9)
• grant_read_oplock(9)
• grant_none_oplock(9)
• same_client_has_lease(9)
• __smb2_oplock_break_noti(9)
• smb2_oplock_break_noti(9)
• __smb2_lease_break_noti(9)
• smb2_lease_break_noti(9)
• smb_grant_oplock(9)
• smb_break_all_write_oplock(9)
• __smb_break_all_levII_oplock(9)
• smb_break_all_oplock(9)
• smb2_map_lease_to_oplock(9)
• create_lease_buf(9)
• parse_lease_state(9)
• smb2_find_context_vals(9)
• create_durable_v2_rsp_buf(9)
• create_mxac_rsp_buf(9)
• create_posix_rsp_buf(9)
• create_aapl_rsp_buf(9)
• lookup_lease_in_table(9)

(also note the __ prefixes on __smb2_oplock_break_noti, __smb2_lease_break_noti and __smb_break_all_levII_oplock, and the capital II in levII — do not come for her, that's literally how they're spelled 💅)

---

real talk though: this page gives you the name, the signature, the one argument and the see-also circle. it does not spell out any return value (there isn't one, it's void) and it does not promise you anything beyond a durable handle context landing in cc. no cap. 🌈

---

and that's the whole page, bestie! source is the kernel tree at ./fs/smb/server, dated October 2026, and it's create_durable_rsp_buf(9) all the way down. slay, go read create_durable_v2_rsp_buf(9) next, she's the sequel 💜🎀