fcoe_ctlr_vn_rport_callback(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… fcoe_ctlr_vn_rport_callback β€” from the Kernel API Manual, bestie ✨

okay so picture this: we're deep in the Kernel API Manual and the function we're stanning today is fcoe_ctlr_vn_rport_callback, aka the literal event handler for rport events. she's giving backstage-pass energy for remote port drama 🎟️✨


πŸ¦‹ NAME πŸ¦‹

fcoe_ctlr_vn_rport_callback β€” Event handler for rport events. that's it, that's the whole job, and she does it flawlessly πŸ’…


🌸 SYNOPSIS 🌸

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

void return, three args, no cap β€” she takes them in and hands nothing back 🫢


πŸŽ€ ARGUMENTS πŸŽ€

  • lport β€” the lport that's receiving the event πŸ‘‘ like, this is the local port catching the whole vibe
  • rdata β€” remote port private data πŸ“ the receipts on the remote port in question
  • event β€” the event that occurred ⭐ literally the thing that happened, that's the whole tea

πŸ”₯ DESCRIPTION πŸ”₯

Locking Note: the rport lock must not be held when you call this function. ngl that's the entire description and it's kinda iconic of her β€” one sentence, zero fluff, maximum consequence 😭 hold that lock and you're in for a bad time, so don't, fr fr πŸ™ˆ


🧚 SEE ALSO 🧚

bestie she has so many friends, it's giving main character with a whole group chat πŸ’œ The kernel file is ./drivers/scsi/fcoe/fcoe_ctlr.c, and here's the entire squad, in order, no skips:

fcoe_ctlr_set_state(9), fcoe_ctlr_mtu_valid(9), fcoe_ctlr_fcf_usable(9), fcoe_ctlr_map_dest(9), fcoe_ctlr_init(9), fcoe_sysfs_fcf_add(9), fcoe_sysfs_fcf_del(9), fcoe_ctlr_reset_fcfs(9), fcoe_ctlr_destroy(9), fcoe_ctlr_announce(9), fcoe_ctlr_fcoe_size(9), fcoe_ctlr_solicit(9), fcoe_ctlr_link_up(9), fcoe_ctlr_reset(9), fcoe_ctlr_link_down(9), fcoe_ctlr_send_keep_alive(9), fcoe_ctlr_encaps(9), fcoe_ctlr_els_send(9), fcoe_ctlr_age_fcfs(9), fcoe_ctlr_parse_adv(9), fcoe_ctlr_recv_adv(9), fcoe_ctlr_recv_els(9), fcoe_ctlr_recv_clr_vlink(9), fcoe_ctlr_recv(9), fcoe_ctlr_recv_handler(9), fcoe_ctlr_select(9), fcoe_ctlr_flogi_send_locked(9), fcoe_ctlr_flogi_retry(9), fcoe_ctlr_flogi_send(9), fcoe_ctlr_timeout(9), fcoe_ctlr_timer_work(9), fcoe_ctlr_recv_work(9), fcoe_ctlr_recv_flogi(9), fcoe_wwn_from_mac(9), fcoe_ctlr_rport(9), fcoe_ctlr_vn_send(9), fcoe_ctlr_disc_stop_locked(9), fcoe_ctlr_disc_stop(9), fcoe_ctlr_disc_stop_final(9), fcoe_ctlr_vn_restart(9), fcoe_ctlr_vn_start(9), fcoe_ctlr_vn_parse(9), fcoe_ctlr_vn_send_claim(9), fcoe_ctlr_vn_probe_req(9), fcoe_ctlr_vn_probe_reply(9), fcoe_ctlr_vn_add(9), fcoe_ctlr_vn_lookup(9), fcoe_ctlr_vn_claim_notify(9), fcoe_ctlr_vn_claim_resp(9), fcoe_ctlr_vn_beacon(9), fcoe_ctlr_vn_age(9), fcoe_ctlr_vn_recv(9), fcoe_ctlr_vlan_parse(9), fcoe_ctlr_vlan_send(9), fcoe_ctlr_vlan_disc_reply(9), fcoe_ctlr_vlan_recv(9), fcoe_ctlr_disc_recv(9), fcoe_ctlr_vn_disc(9), fcoe_ctlr_vn_timeout(9), fcoe_ctlr_mode_set(9), fcoe_libfc_config(9)

like I said. a whole group chat πŸ«ΆπŸ’–


✨ cute lil sign-off time ✨ this page lives in ./drivers/scsi/fcoe and it's dated October 2026, so go forth, don't hold that rport lock, and slay πŸ’…πŸŽ€πŸ’–
πŸ“¦ where this page comes from