fc_lport_error(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… fc_lport_error(9) πŸ’…

okay so this page is straight out of the Kernel API Manual and it's about fc_lport_error β€” the handler for any errors. yes, any. it's giving "catch-all bestie who handles everyone's drama" energy 🫢


✨ NAME ✨

fc_lport_error β€” handler for any errors πŸ’…


πŸŽ€ SYNOPSIS πŸŽ€

void fc_lport_error (struct fc_lport *lport , struct fc_frame *fp );

like, that's the whole signature. short king. πŸ‘‘


πŸ¦‹ ARGUMENTS πŸ¦‹

  • lport β€” the local port that the error was on. that's the one having a bad day, not you. πŸ’–
  • fp β€” the error code encoded in a frame pointer. yes bestie, the error code is inside the frame pointer. iykyk. πŸ”₯

🌸 DESCRIPTION 🌸

okay so here's the tea β˜• β€” if the error was caused by a resource allocation failure, then you wait for half a second and retry. literally just a lil nap and then try again, no cap 😴✨

otherwise (i.e. it's not a resource allocation failure), you retry after the e_d_tov time instead. that's the vibe. different error, different waiting period, periodt. πŸ’€


🌈 SEE ALSO 🌈

lowkey a whole friend group in here, ngl. the kernel file we're repping is ./drivers/scsi/libfc/fc_lport.c and the struct is struct fc_bsg_info(9). and then, in the order the page gives them (no cap, i'm not reordering anyone's friendship group):

like i said. a whole friend group. go say hi to all of them πŸ‘‹πŸ’œ


and that's the page!! shoutout to the ./drivers/scsi/libfc source and the October 2026 date on this one β€” the version info lives down at the bottom of the original, so consider this your cute lil sign-off πŸŽ€βœ¨ slay, bye bestie πŸ’–

πŸ“¦ where this page comes from