nfs_find_best_sec(9)

💅 nfs_find_best_sec(9) 💅

okay so bestie, welcome to the Kernel API Manual — this one's a 9 section page, kernel internals, very main character energy. We're talking about nfs_find_best_sec — the little function that goes "which security flavor do we all actually vibe with?" 🦋

---

✨ NAME ✨

nfs_find_best_sec — find a security mechanism supported locally 🌸

---

🎀 SYNOPSIS 🎀

struct rpc_clnt * nfs_find_best_sec (struct rpc_clnt *clnt , struct
nfs_server *server , struct nfs4_secinfo_flavors *flavors );

---

🫶 ARGUMENTS 🫶

• clnt — pointer to rpc_clnt. just a lil pointer, she's just standing there 💅
• server — the NFS server struct, iykyk
• flavors — the list of security tuples that came back from the SECINFO procedure ✨

---

🔥 DESCRIPTION 🔥

So what she does: she returns an rpc client that uses the first security mechanism in flavors that is locally supported. Literally the first one that works for us, no cap. 👑

The flavors array gets searched in the order returned from the server, per the RFC 3530 recommendation — the server's order is the order, periodt. And each flavor gets checked for membership in the sec= mount option list, if it exists. (key words: if it exists 🫶)

⚠️ If no matching flavor is found in the array, she returns -EPERM. no match, no vibe check passed, that's the rule 😭

🚨 Please call rpc_shutdown_client when you are done with this rpc client. like actually. don't just ghost it, clean up after yourself bestie 💀

---

🌈 SEE ALSO 🌈

• Kernel file ./fs/nfs/nfs4namespace.c
• nfs4_negotiate_security(9)
• nfs_follow_referral(9)
• nfs4_replace_transport(9)

---

and that's the whole page, bestie, we ate and left no crumbs 🍓✨ she lives in ./fs/nfs, dated October 2026, and she answers to the name nfs_find_best_sec(9) — mwah 💋🎀