fc_rport_enter_delete(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸŽ€ fc_rport_enter_delete(9) πŸŽ€

okay bestie, welcome to the Kernel API Manual page for fc_rport_enter_delete(9) β€” the one about scheduling a remote port to be deleted. It's giving kernel-internals main character energy, and we're gonna make it make sense. πŸ’…βœ¨


🌸 NAME 🌸

  • fc_rport_enter_delete β€” Schedule a remote port to be deleted.

✨ SYNOPSIS ✨

       void fc_rport_enter_delete (struct fc_rport_priv *rdata , enum
       fc_rport_event event );

πŸ’… ARGUMENTS πŸ’…

  • rdata β€” The remote port to be deleted.
  • event β€” The event to report as the reason for deletion.

πŸ¦‹ DESCRIPTION πŸ¦‹

okay so, here's the tea: this function allows the state change into DELETE only once. It calls queue_work only if there's no event already pending. It sets the new event so that the old pending event will not occur. And since we have the mutex, even if fc_rport_work is already started, it'll see the new event. No cap. 🫢

Reference counting: it does not modify kref.

πŸ”₯ SEE ALSO πŸ”₯

Peep the kernel file ./drivers/scsi/libfc/fc_rport.c β€” and here's the whole FC bestie lineup, in the exact order the page gives them:


source/version footer says ./drivers/scsi/libfc, the date on the page is October 2026, and this has been fc_rport_enter_delete(9) from the Kernel API Manual β€” bye bestie, go schedule that deletion responsibly πŸ’–πŸ¦‹

πŸ“¦ where this page comes from