summaryrefslogtreecommitdiffstats
path: root/mm/slab_common.c
diff options
context:
space:
mode:
authorJohn Garry <john.garry@huawei.com>2019-04-12 10:57:56 +0200
committerMartin K. Petersen <martin.petersen@oracle.com>2019-04-16 00:55:01 +0200
commitd8649fc1c5e40e691d589ed825998c36a947491c (patch)
treeb0cbf9932a4cb53546694e63a02afb858bfb5b5d /mm/slab_common.c
parentscsi: libsas: Inject revalidate event for root port event (diff)
downloadlinux-d8649fc1c5e40e691d589ed825998c36a947491c.tar.xz
linux-d8649fc1c5e40e691d589ed825998c36a947491c.zip
scsi: libsas: Do discovery on empty PHY to update PHY info
When we discover the PHY is empty in sas_rediscover_dev(), the PHY information (like negotiated linkrate) is not updated. As such, for a user examining sysfs for that PHY, they would see incorrect values: root@(none)$ cd /sys/class/sas_phy/phy-0:0:20 root@(none)$ more negotiated_linkrate 3.0 Gbit root@(none)$ echo 0 > enable root@(none)$ more negotiated_linkrate 3.0 Gbit So fix this, simply discover the PHY again, even though we know it's empty; in the above example, this gives us: root@(none)$ more negotiated_linkrate Phy disabled We must do this after unregistering the device associated with the PHY (in sas_unregister_devs_sas_addr()). Signed-off-by: John Garry <john.garry@huawei.com> Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
Diffstat (limited to 'mm/slab_common.c')
0 files changed, 0 insertions, 0 deletions