fc_disc_error(9)

💅 fc_disc_error — a.k.a. the "oops, the dNS request glitched" handler 💅

okay bestie, so this page is from the Kernel API Manual, and it's about fc_disc_error(9) — the little function whose whole personality is dealing with an error on a dNS request. That's it, that's the vibe. Short page, iconic energy, let's go 🎀

---

✨ NAME ✨

fc_disc_error — Handle error on dNS request 🔥

Like, literally. Something went sideways with a dNS request and this function is the main character that steps in to handle it. No cap.

---

🌸 SYNOPSIS 🌸

void fc_disc_error (struct fc_disc *disc , struct fc_frame *fp );

Return type is void, so it's giving "I do the work and I don't report back" energy. Respect. 💅

---

🦋 ARGUMENTS 🦋

• disc — The discovery context 👑 — this is the whole discovery situation this error is happening inside of.
• fp — The error code encoded as a frame pointer 🌈 — yes bestie, the error code is smuggled inside a frame pointer. That's the bitcast lifestyle, iykyk.

---

🫶 SEE ALSO 🫶

The kernel file ./drivers/scsi/libfc/fc_disc.c is the home base 🏠, and it's surrounded by the whole friend group of discovery functions — go say hi to all of them:

• fc_disc_stop_rports(9)
• fc_disc_recv_rscn_req(9)
• fc_disc_recv_req(9)
• fc_disc_restart(9)
• fc_disc_start(9)
• fc_disc_done(9)
• fc_disc_gpn_ft_req(9)
• fc_disc_gpn_ft_parse(9)
• fc_disc_timeout(9)
• fc_disc_gpn_ft_resp(9)
• fc_disc_gpn_id_resp(9)
• fc_disc_gpn_id_req(9)
• fc_disc_single(9)
• fc_disc_stop(9)
• fc_disc_stop_final(9)
• fc_disc_config(9)
• fc_disc_init(9)

All seventeen of them 💖 not one less, we don't do incomplete reference lists in this house.

---

quick vibe check: this page has exactly one job, one function, two arguments, and a whole lot of sibling functions. That's the whole story, and honestly? Slay. ⭐

---

and that's the whole page, bestie 🎀 sign-off time: this lil number lives over in ./drivers/scsi/libfc, and it's dated October 2026 ✨ periodt 💜