_scsih_searc...ng_expanders(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– NAME

_scsih_searc...ng_expanders β€” yes bestie, that's the whole name, ellipsis and all, she's mysterious like that πŸ’… (this is a page from the Kernel API Manual, and we are so glad you're here).

✨ SYNOPSIS

void _scsih_searc...ng_expanders (struct MPT3SAS_ADAPTER *ioc );

Return type: void, so like… she gives nothing back. Zero notes. Iconic. 🫢

πŸŽ€ ARGUMENTS

  • ioc β€” the per adapter object πŸ¦‹. That's it, that's the whole argument list. One (1) bestie. Her whole world.

🌸 DESCRIPTION

Okay so picture this: the host just got reset (rough day for her, honestly 😭), and now we gotta go around asking every device "hi, are you still there?? are you okay??" πŸ“ž

If a device is not responding β€” no cap β€” we remove it. That's the whole vibe check. Bye bestie, we hardly knew ye πŸ’€

Fr fr though, that's the entire behavior: after host reset, find out whether devices are still responding. If not, remove. No extra secret sauce, don't let anyone tell you otherwise πŸ™ˆ

🌈 SEE ALSO

The kernel file for all of this lives at ./drivers/scsi/mpt3sas/mpt3sas_scsih.c β€” go say hi πŸ‘‘

And the enum device_responsive_state(9), plus literally the entire mpt3sas extended family, all here for your scrolling pleasure:


That's the whole page, bestie, you ate that πŸ“βœ¨ This one came from the source tree at ./drivers/scsi/mpt3sas and it's dated October 2026, all wrapped up under the title _scsih_searc...ng_expanders(9) from the Kernel API Manual. Go be the main character of your own driver πŸŒˆπŸ‘‘

πŸ“¦ where this page comes from