create_aapl_rsp_buf(9)

🍓 create_aapl_rsp_buf(9) — like, the whole vibe ✨

okay so bestie, welcome to the Kernel API Manual entry for create_aapl_rsp_buf(9) 💅 this is the one that builds the AAPL kAAPL_SERVER_QUERY response, and honestly? it's giving niche-but-iconic. sit down, grab a boba, we're doing this 🧚

---

🌸 NAME 🌸

create_aapl_rsp_buf — build AAPL kAAPL_SERVER_QUERY response ✨

---

🎀 SYNOPSIS 🎀

void create_aapl_rsp_buf (char *cc , __u64 vol_caps , __u64 req_bitmap ,
bool readdir_attr_v2 );

that's it. that's the signature. no cap, she's compact 🔥

---

💖 ARGUMENTS 💖

• cc — the buffer you write the create context into. it has to be AAPL_RSP_MAX_SIZE bytes, so like… don't skimp, she needs room 🎀
• vol_caps — the volume capability flags, aka the SMB2_CRTCTX_AAPL_* volume bits 👑
• req_bitmap — the client's request bitmap. we literally echo it right back in reply_bitmap, it's a whole mirror moment 🪞
• readdir_attr_v2 — set this and we advertise SMB2_CRTCTX_AAPL_SUPPORTS_READ_DIR_ATTR_V2 instead of the V1 bit. glow-up behavior fr fr ✨

---

🦋 DESCRIPTION 🦋

So the response format follows the exact layout observed from macOS's own smbd, and it matches the client-side parsing in AAPL's published public client kernel source — specifically the public client behavior reference, kAAPL_SERVER_QUERY case 👀 like, we're being faithful to the source material, periodt.

The layout goes: reply_bitmap first, and then the server_caps / vol_caps / model-info fields are present only when their reply_bitmap bit is set 🫶

• reply_bitmap = req_bitmap masked to the fields we support 💅
• server_caps = AAPL_SERVER_CAPS_KSMBD when requested 🌟
• vol_caps = caller-supplied, you bring your own, we don't judge 💜
• model string = server_conf.aapl_model (default "Xserve") in UTF-16LE, when SMB2_CRTCTX_AAPL_MODEL_INFO is requested 🎀

⚠️ okay serious moment, bestie, listen: sending reply_bitmap with MODEL_INFO set but no model string causes smbfs.kext to enter a broken disconnect path requiring a macOS reboot. 😭💀 like, not cute. not the vibe. don't do it. that's a whole system reboot because of one missing string, and we are NOT about that life.

---

🌈 SEE ALSO 🌈

Kernel file ./fs/smb/server/oplock.c and honestly her whole extended friend group 💅:

• 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_rsp_buf(9)
• create_durable_v2_rsp_buf(9)
• create_mxac_rsp_buf(9)
• create_posix_rsp_buf(9)
• lookup_lease_in_table(9)

---

⭐ bye bestie ⭐

this whole page lives in ./fs/smb/server, dated October 2026, and it's filed under create_aapl_rsp_buf(9) in the Kernel API Manual — mwah, stay hydrated, don't forget your MODEL_INFO string, and slay your SMB queries responsibly 🫶💖🎀🌈