nvme_fc_rescan_remoteport(9)

✨ nvme_fc_rescan_remoteport ✨

okay so bestie, welcome to the Kernel API Manual entry for nvme_fc_rescan_remoteport(9) — yes that's a whole mouthful, yes it's iconic, and yes we're gonna get through it together 💅

---

🌸 NAME 🌸

nvme_fc_rescan_remoteport — the transport entry point that an LLDD calls when it wants an nvme device rescan to happen. like, it's the little knock on the door that says "hey, look at this port again bestie" 🫶

---

🦋 SYNOPSIS 🦋

void nvme_fc_rescan_remoteport (struct nvme_fc_remote_port *remoteport
);

that's it. that's the whole vibe check. no hidden tricks, no surprise returns, just one function taking one pointer ✨

---

🎀 ARGUMENTS 🎀

• remoteport — pointer to the (registered) remote port that is to be rescanned. key word being registered, bestie, it's right there in the parentheses. this is the port you're asking the kernel to go give another look 👀🔥

---

💜 RETURN 💜

N/A — literally nothing comes back. it's a void function, so don't be out here waiting for a return value that's never gonna text you back 😭💀

---

🌈 SEE ALSO 🌈

• Kernel file ./drivers/nvme/host/fc.c — that's where the whole thing lives, the main character file itself 👑
• nvme_fc_register_localport(9)
• nvme_fc_unregister_localport(9)
• nvme_fc_register_remoteport(9)
• nvme_fc_unregister_remoteport(9)
• nvme_fc_rcv_ls_req(9)

like, the whole friend group fr fr — register and unregister for both local and remote ports, plus nvme_fc_rcv_ls_req(9). go read them, they ate 💅

---

lowkey a reminder: the port you pass in has to be a registered remote port. don't be passing random pointers and then acting surprised, ngl 🙈

---

and that's the page, bestie! 🎉 this whole thing comes from the source at ./drivers/nvme/host, dated October 2026 — so go forth, rescan responsibly, and slay 💖🦋🎀⭐🍓