fc_lport_rport_callback(9)

💅 fc_lport_rport_callback — like, the rport event handler bestie

ok so this is a page out of the Kernel API Manual, and it's all about fc_lport_rport_callback. Buckle up, it's short but it matters 🎀

---

✨ NAME ✨

fc_lport_rport_callback — the event handler for rport events, periodt 💫

---

🌸 SYNOPSIS 🌸

void fc_lport_rport_callback (struct fc_lport *lport , struct
fc_rport_priv *rdata , enum fc_rport_event event );

that's the whole signature, no cap. three args, one void return, she's giving "I just handle events and leave" energy 👑

---

🦋 ARGUMENTS 🦋

• lport — the lport that's receiving the event. she's the one getting the news 📬
• rdata — private remote port data. the lore, basically 🙈
• event — the event that actually went down. the main character of the whole function ngl ⭐

---

💖 DESCRIPTION 💖

Locking Note: the rport lock should not be held when you call this function. like, genuinely, do not. that's the entire description and it's lowkey the most important sentence on this page 😭🔒

---

🌈 SEE ALSO 🌈

ok this list is long but we do not skip a single one, iykyk. first up, the kernel file: Kernel file ./drivers/scsi/libfc/fc_lport.c — and then the whole friend group:

struct fc_bsg_info(9), fc_frame_drop(9), fc_lport_state(9), fc_lport_ptp_setup(9), fc_get_host_port_state(9), fc_get_host_speed(9), fc_get_host_stats(9), fc_lport_flogi_fill(9), fc_lport_add_fc4_type(9), fc_lport_recv_rlir_req(9), fc_lport_recv_echo_req(9), fc_lport_recv_rnid_req(9), fc_lport_recv_logo_req(9), fc_fabric_login(9), __fc_linkup(9), fc_linkup(9), __fc_linkdown(9), fc_linkdown(9), fc_fabric_logoff(9), fc_lport_destroy(9), fc_set_mfs(9), fc_lport_disc_callback(9), fc_lport_enter_ready(9), fc_lport_set_port_id(9), fc_lport_set_local_id(9), fc_lport_recv_flogi_req(9), fc_lport_recv_els_req(9), fc_lport_recv(9), fc_lport_reset(9), fc_lport_reset_locked(9), fc_lport_enter_reset(9), fc_lport_enter_disabled(9), fc_lport_error(9), fc_lport_ns_resp(9), fc_lport_ms_resp(9), fc_lport_scr_resp(9), fc_lport_enter_scr(9), fc_lport_enter_ns(9), fc_lport_enter_dns(9), fc_lport_enter_ms(9), fc_lport_enter_fdmi(9), fc_lport_timeout(9), fc_lport_logo_resp(9), fc_lport_enter_logo(9), fc_lport_flogi_resp(9), fc_lport_enter_flogi(9), fc_lport_config(9), fc_lport_init(9), fc_lport_bsg_resp(9), fc_lport_els_request(9), fc_lport_ct_request(9), fc_lport_bsg_request(9)

every single one is invited to the party, nobody gets left on read 🫶🎀

---

💀 tiny reminder bestie: lport receives, rdata is the private remote port data, event is what happened — and no rport lock when calling. that's the whole vibe check.

---

and that's a wrap!! this page lives in ./drivers/scsi/libfc in the Kernel API Manual, dated October 2026 🌸 thanks for reading, ily, go handle those events responsibly 💜✨