966944d6d8
smartpqi uses scsi_transport_sas but does not register a sas_host object, so /sys/class/sas_host/host14 does not exist and the existing SAS detection check passes right through. Writing to host14/scan then calls sas_user_scan which blocks indefinitely on scsi_scan_target's mutex (confirmed by kernel hung-task traces in the field). Add a second detection path via /sys/class/scsi_host/hostX/proc_name: skip hosts whose driver is "smartpqi" or "hpsa" (HPE Smart Array predecessors that exhibit the same behaviour). Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>