fc_remove_host(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ¦‹ fc_remove_host(9) β€” Kernel API Manual πŸ¦‹

okay bestie, this is the Kernel API Manual page for fc_remove_host(9), and it's literally about cleaning up your fc_transport situation before things get cursed πŸ’…

πŸ’– NAME πŸ’–

fc_remove_host β€” called to terminate any fc_transport-related elements for a scsi host. That's the whole vibe: break down the fc_transport stuff tied to a SCSI host ✨

✨ SYNOPSIS ✨

void fc_remove_host (struct Scsi_Host *shost );

πŸŽ€ ARGUMENTS πŸŽ€

  • shost β€” Which Scsi_Host πŸ’– (yep, that's the argument, and it tells the routine which host we're talking about)

πŸ”₯ DESCRIPTION πŸ”₯

Okay so the expectation is that you call this routine immediately preceding the driver's call to scsi_remove_host β€” and yes, the original wording says β€œthe a driver's call”, so we're preserving that little artifact, no cap 😭. Before, not after, not whenever.

⚠️ WARNING: A driver utilizing the fc_transport, which fails to call this routine prior to scsi_remove_host, will leave dangling objects in /sys/class/fc_remote_ports. Access to any of these objects can result in a system crash !!! This is not a drill, bestie πŸ’€

🧚 NOTES 🧚

Lock vibe check: this routine assumes no locks are held on entry. None. Zero. Do not walk in holding a lock like it's a Starbucks cup πŸ”’πŸ™…β€β™€οΈ

🌈 SEE ALSO 🌈

Kernel file ./drivers/scsi/scsi_transport_fc.c plus the whole function family reunion:


okay that's the page, mwah πŸ’‹ β€” source/version: ./drivers/scsi; date: October 2026; manual: fc_remove_host(9). byeee 🫢✨

πŸ“¦ where this page comes from