nfs4_discov...ver_trunking(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… nfs4_discov...ver_trunking(9) πŸ’…

okay so bestie, welcome to the Kernel API Manual β€” yes, that Kernel API Manual β€” and today's main character is nfs4_discover_server_trunking. it's giving networking detective energy and honestly? iconic. πŸ•΅οΈβ€β™€οΈβœ¨


🌸 NAME 🌸

nfs4_discover_server_trunking β€” detect server IP address trunking πŸ’–

like. it finds out whether the server is doing the trunking thing. that's the whole vibe. 😌


✨ SYNOPSIS ✨

int nfs4_discover_server_trunking (struct nfs_client *clp , struct
       nfs_client **result );

literally right there. two arguments. one int coming back at you. slay. 🫢


πŸŽ€ ARGUMENTS πŸŽ€

  • clp β€” the nfs_client under test πŸ” like the one we're putting in the hot seat, ngl
  • result β€” OUT: found nfs_client, or clp 🌟 so it's an output param, and what lands in it is either the nfs_client we found or just clp itself. iykyk

πŸ¦‹ DESCRIPTION πŸ¦‹

returns zero or a negative errno. periodt. πŸ’…

and if zero comes back? that means an nfs_client pointer gets planted in "result". yup, zero is the good one, the pointer shows up, the whole thing ate. πŸ‘‘


⭐ NOTE ⭐

heads up bestie, this one's important: since we are invoked in process context, and not from inside the state manager, we cannot use nfs4_handle_reclaim_lease_error. 😭 no cap. that function is just not available to us here. don't try it, the vibe check says no. πŸ™ˆ

🧚 SEE ALSO 🧚

kernel file ./fs/nfs/nfs4state.c and the whole friend group 🌈:


and that's the page!! πŸŽ‰ source spot is ./fs/nfs, dated October 2026 β€” mwah, kisses, go read the kernel source bestie πŸ’œπŸ“πŸ§šβ€β™€οΈ

πŸ“¦ where this page comes from