sas_get_address(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

🌸 sas_get_address β€” the kernel API manual, bestie edition 🌸

Okay so you found yourself in section 9 of the kernel API manual (yes, the fancy kernel-only one, not your regular userland pages πŸ’…) and you want the tea on sas_get_address. Pull up a chair, this one's short but it slaps.


✨ NAME ✨

sas_get_address β€” literally just returns the SAS address of the device πŸ’–

Like, that's it. That's the whole job. King behavior tbh πŸ‘‘


πŸŽ€ SYNOPSIS πŸŽ€

u64 sas_get_address (struct scsi_device *sdev );

Note the return type, bestie: a u64. It's giving "big number, no decimals, don't ask questions" energy πŸ”₯


πŸ¦‹ ARGUMENTS πŸ¦‹

  • sdev β€” the scsi device 🫢 your little SCSI friend that you're asking about. Hand it over and it'll tell you its SAS address.

πŸ’œ DESCRIPTION πŸ’œ

Returns the SAS address of the scsi device ✨

That's the entire description. No disclaimers, no caveats, no "undefined behavior if you sneeze wrong" β€” just a clean little getter doing its one (1) job and doing it well. Obsessed, honestly 😭


🌈 SEE ALSO 🌈

Bestie, this is the part where the page absolutely ate β€” the sibling squad is huge. Every single one of these lives in the kernel file ./drivers/scsi/scsi_transport_sas.c, and here's the full guest list πŸŽ€:

Phy girlies, port girlies, rphy girlies, transport girlies β€” everyone showed up. The whole function family is main character energy πŸ‘‘πŸ’…


Heads up bestie: every single one of those references is written exactly as it appears in the manual, section (9) and all. Don't go removing the numbers, iykyk 🫢

🧚 cute little sign-off 🧚

This page comes to you straight from the source directory ./drivers/scsi, and it's dated October 2026 ⭐ Keep it in your back pocket, and go get that SAS address, bestie. Slay πŸ’–βœ¨πŸ“

πŸ“¦ where this page comes from