smb2_parse_...te_transform(9)

💅 smb2_parse_rdma_write_transform(9) 💅

ok so this is from the Kernel API Manual bestie, section 9, and the vibe is very "kernel dev who actually reads the spec" ✨

---

🌸 NAME 🌸

smb2_parse_rdma_write_transform — the function that validates your RDMA WRITE transform metadata 🫶

Like no cap, that's literally its whole job. It's the bouncer at the club door checking everyone's ID before they get in 💅

---

✨ SYNOPSIS ✨

int smb2_parse_rdma_write_transform (struct ksmbd_work *work , struct
smb2_write_req *req , struct smb2_rdma_write_transform *info );

three args, one int back, classic. it's giving "small function, big responsibility" energy honestly 👑

---

🎀 ARGUMENTS 🎀

• work — the request work item 🧚 like the lil context bundle for the request you're currently handling
• req — the WRITE request containing the transform 💖 that's the one you're pulling the transform out of
• info — parsed transform information 🌸 where the good stuff ends up after parsing

---

🦋 DESCRIPTION 🦋

ok so here's the tea ☕ this function checks all the things:

• transform counts ✅
• crypto fields ✅
• descriptor alignment and bounds ✅
• negotiated algorithms ✅
• the nested RDMA channel ✅

that's it, that's the whole checklist. it validates them. all of them. fr fr, if any of that is off, this is not the moment where you get a cute little warning — it's just not passing go 🚫

think of it as the vibe check for RDMA WRITE transforms, and the vibe check is strict 💀

---

🔥 RETURN 🔥

• 0 on success 🎉 slay, we parsed
• otherwise, a negative errno 😭 that's your "nope" signal

---

🌈 SEE ALSO 🌈

bestie I'm not gonna lie, this list is long, and every single one of these is iconic in its own way. no cap, here's the full roster 👑

• Kernel file ./fs/smb/server/smb2pdu.c
• smb2_get_ksmbd_tcon(9)
• smb2_set_err_rsp(9)
• is_smb2_neg_cmd(9)
• is_smb2_rsp(9)
• get_smb2_cmd_val(9)
• set_smb2_rsp_status(9)
• init_smb2_neg_rsp(9)
• smb2_set_rsp_credits(9)
• init_chained_smb2_rsp(9)
• is_chained_smb2_message(9)
• init_smb2_rsp_hdr(9)
• smb2_allocate_rsp_buf(9)
• smb2_check_user_session(9)
• smb2_get_name(9)
• smb2_get_dos_mode(9)
• build_rdma_ctx(9)
• smb3_encryption_negotiated(9)
• decode_rdma_ctx(9)
• smb2_handle_negotiate(9)
• smb2_tree_connect(9)
• smb2_create_open_flags(9)
• smb2_tree_disconnect(9)
• smb2_session_logoff(9)
• create_smb2_pipe(9)
• smb2_set_ea(9)
• smb2_open(9)
• smb2_populate_readdir_entry(9)
• buffer_check_err(9)
• smb2_get_ea(9)
• smb2_query_info(9)
• smb2_close_pipe(9)
• smb2_close(9)
• smb2_echo(9)
• smb2_set_info_file(9)
• smb2_set_info(9)
• smb2_read_pipe(9)
• smb2_set_rdma_key(9)
• smb2_prep_rdma_read(9)
• smb2_current_req_len(9)
• check_rdma_desc(9)
• smb2_read_rdma(9)
• smb2_read(9)
• smb2_write_pipe(9)
• smb2_write_rdma(9)
• smb2_write(9)
• smb2_flush(9)
• smb2_cancel(9)
• smb2_lock(9)
• smb2_ioctl(9)
• smb20_oplock_break_ack(9)
• smb21_lease_break_ack(9)
• smb2_oplock_break(9)
• smb2_notify(9)
• smb2_is_sign_req(9)
• smb2_check_sign_req(9)
• smb2_get_sign_rsp_iov(9)
• smb2_set_sign_rsp(9)
• smb3_check_sign_req(9)
• smb3_set_sign_rsp(9)
• smb3_preauth_hash_rsp(9)

seriously, go read some of these when you get a sec, they're lowkey all connected 🫶 iykyk

---

okay that's the page!! this one lives in ./fs/smb/server and it was dated October 2026 🌸 so yeah, go forth and validate those transforms bestie, u got this 💜✨🎀