diff options
author | 2024-03-07 14:14:13 +0000 | |
---|---|---|
committer | 2024-03-10 18:02:54 -0400 | |
commit | 8e68a458bcf5b5cb9c3624598bae28f08251601f (patch) | |
tree | 04b8e264fd97936741da0562c5d8f2ed2ecf7532 /scripts/gdb/linux/utils.py | |
parent | scsi: libsas: Add a helper sas_get_sas_addr_and_dev_type() (diff) | |
download | linux-rng-8e68a458bcf5b5cb9c3624598bae28f08251601f.tar.xz linux-rng-8e68a458bcf5b5cb9c3624598bae28f08251601f.zip |
scsi: libsas: Fix disk not being scanned in after being removed
As of commit d8649fc1c5e4 ("scsi: libsas: Do discovery on empty PHY to
update PHY info"), do discovery will send a new SMP_DISCOVER and update
phy->phy_change_count. We found that if the disk is reconnected and phy
change_count changes at this time, the disk scanning process will not be
triggered.
Therefore, call sas_set_ex_phy() to update the PHY info with the results of
the last query. And because the previous phy info will be used when calling
sas_unregister_devs_sas_addr(), sas_unregister_devs_sas_addr() should be
called before sas_set_ex_phy().
Fixes: d8649fc1c5e4 ("scsi: libsas: Do discovery on empty PHY to update PHY info")
Signed-off-by: Xingui Yang <yangxingui@huawei.com>
Link: https://lore.kernel.org/r/20240307141413.48049-3-yangxingui@huawei.com
Reviewed-by: John Garry <john.g.garry@oracle.com>
Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
Diffstat (limited to 'scripts/gdb/linux/utils.py')
0 files changed, 0 insertions, 0 deletions