sas_port_free(9)

📦 version 7.3.1, in nixpkgs unstable

💅 sas_port_free — okay so this is the sas_port_free(9) page, bestie

Welcome to the Kernel API Manual, genuinely the group chat you never asked to join but now can't leave. Today's main character: sas_port_free, a little function with one job and zero hesitation.

✨ NAME ✨

sas_port_free — frees a SAS PORT. That's it. That's the whole personality. 🎀

🌸 SYNOPSIS 🌸

void sas_port_free (struct sas_port *port );

Note the void up front, okay? This one returns literally nothing. No status, no error code, no little note passed back to you. It does the thing and dips. 💅

🦋 ARGUMENTS 🦋

  • port — the SAS PORT you want to free. That's the one. Hand it over and it gets freed. 🫶

⭐ DESCRIPTION ⭐

It frees the specified SAS PORT.

Honestly? No notes. It's giving "short king, gets the job done." You point at a port, the port gets freed, everyone goes home. 🔥

💀 NOTE 💀

Okay this is the important part, so like, read it, bestie. 😭

This function must only be called on a PORT that has not successfully been added using sas_port_add.

So if sas_port_add already went through and did its little slay? Do not come for this function. That's not the vibe. Use the correct lifecycle call for a port that's actually been added — sas_port_free is for the ones that never made it in. Periodt.

🌈 SEE ALSO 🌈

Kernel file ./drivers/scsi/scsi_transport_sas.c

The whole friend group, in original order, no cap:

Twenty-nine links, and yes I counted. Obsessed with whoever maintains this index. 👑

And that's the whole page, bestie! 💖 This one lives in ./drivers/scsi and it's dated October 2026, which is like, somehow both the past and the future depending on when you're reading this, and honestly? Iconic. Go free your ports responsibly. 🧚✨

📦 where this page comes from