mpt3sas_get_sdev_by_handle(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

okay so real talk, this is a page from the Kernel API Manual (section 9, kernel internals, we're in the deep end bestie and it's honestly iconic in here). Let's get into it ✨


🌸 NAME 🌸

mpt3sas_get_sdev_by_handle β€” sas device search, literally what it says on the tin πŸŽ€


✨ SYNOPSIS ✨

struct _sas_device * mpt3sas_get_sdev_by_handle (struct MPT3SAS_ADAPTER
*ioc , u16 handle );

so you hand it an adapter and a handle and it hands you back a struct _sas_device *, slay πŸ’…


🫢 ARGUMENTS 🫢

  • ioc β€” the per adapter object. like, the main character of your adapter's whole life fr πŸ’–
  • handle β€” the sas device handle, and no you don't make this yourself, it's assigned by firmware πŸ‘‘

πŸ”₯ CONTEXT πŸ”₯

the calling function should acquire ioc->sas_device_lock before doing any of this. this is not a drill bestie, take the lock πŸ”’ no cap, skipping it is giving chaos gremlin energy and you do not want that πŸ’€


🌈 DESCRIPTION 🌈

so here's the vibe: this searches for a sas_device based on sas_address, then returns the sas_device object. that's it, that's the whole function, and honestly? she's efficient πŸ’…βœ¨


πŸ¦‹ SEE ALSO πŸ¦‹

bestie. sit down. grab a snack πŸ“. this list is long long, like, the whole mpt3sas_scsih.c family reunion, and every single one of them had to come:


and that's the whole friend group πŸ˜­πŸ’œ

okay byeee, this page lives at ./drivers/scsi/mpt3sas, dated October 2026, and she's filed under mpt3sas_get_sdev_by_handle(9) β€” mwah, go take your lock and stay hydrated πŸ§šβ­πŸŽ€

πŸ“¦ where this page comes from