nfs4_detect_...ion_trunking(9)

💅 nfs4_detect_session_trunking(9) — like, the kernel API manual bestie 🦋

okay so this is a page from the Kernel API Manual and it's all about nfs4_detect_session_trunking — yes that's the full name, and yes the header is truncated as nfs4_detect_...ion_trunking(9) because even man pages gotta keep it cute and fit on one line 💀

---

✨ NAME ✨

nfs4_detect_session_trunking — literally just checks for session trunking. that's the whole vibe check 🔥

---

🌸 SYNOPSIS 🌸

int nfs4_detect_session_trunking (struct nfs_client *clp , struct
nfs41_exchange_id_res *res , struct rpc_xprt *xprt );

---

🎀 ARGUMENTS 🎀

• clp — the original mount nfs_client. like, the OG, the main character 👑
• res — the result structure from an exchange_id that used the original mount nfs_client with a new multi_addr transport. yeah, it's giving "same client, new transport" energy 💫
• xprt — pointer to the transport to add. we're bringing a new one into the group chat 🫶

---

💖 DESCRIPTION 💖

so this gets called after a successful EXCHANGE_ID on a multi-addr connection. that's the whole setup. and then? upon success, add the transport. slay, that's it ✨

returns zero on success — otherwise -EINVAL. no cap, that's the whole return contract 🙈

---

⭐ NOTE ⭐

okay bestie, important detail here 👀 since the exchange_id for the new multi_addr transport uses the same nfs_client from the original mount, the cl_owner_id is reused — which means eir_clientowner is the same. same owner, different transport, iykyk 💅

---

👑 SEE ALSO 👑

kernel file ./fs/nfs/nfs4client.c plus the whole squad:

• nfs4_find_ds_client(9)
• nfs4_find_or_create_ds_client(9)
• nfs41_init_client(9)
• nfs4_init_client(9)
• nfs41_walk_client_list(9)
• nfs4_update_server(9)

---

that's the page, periodt 🌈 and a little sign-off for you: this one lives in ./fs/nfs, dated October 2026 — so mark your calendar, bestie 🗓️💜