scsi: libsas: Support SATA PHY connection rate unmatch fixing during discovery
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Fix Released
|
Undecided
|
dann frazier | ||
Xenial |
Won't Fix
|
Undecided
|
Unassigned | ||
Bionic |
Won't Fix
|
Undecided
|
dann frazier | ||
Cosmic |
Won't Fix
|
Undecided
|
dann frazier | ||
Disco |
Fix Released
|
Undecided
|
dann frazier |
Bug Description
[Impact]
SATA disks may be unusable
will not be usable when:
- The disk is connected through a SAS expander
- Controller uses a libsas-based driver (mvsas, aic94xx, hisi_sas)
- link rate between expander & disk is greater than link between controller and expander
This is unlikely to occur in any production environment, but has occurred in early silicon testing. Fixing this would be helpful in those environments.
[Test Case]
See conditions in "Impact"
Can be simulated with:
for f in /sys/class/
echo "3.0 Gbit" | sudo tee $f
done
[Fix]
cec9771d2e954 scsi: libsas: Support SATA PHY connection rate unmatch fixing during discovery
[Regression Risk]
Impact is restricted to drivers that use libsas: mvsas, aic94xx & hisi_sas.
Code change is all within an "if" statement that meets these restrictions.
A bug in this code could possibly reduce the speed of an otherwise working disk connection.
CVE References
Changed in linux (Ubuntu Disco): | |
status: | New → In Progress |
assignee: | nobody → dann frazier (dannf) |
description: | updated |
Changed in linux (Ubuntu Cosmic): | |
status: | New → In Progress |
Changed in linux (Ubuntu Bionic): | |
status: | New → In Progress |
Changed in linux (Ubuntu Cosmic): | |
assignee: | nobody → dann frazier (dannf) |
Changed in linux (Ubuntu Bionic): | |
assignee: | nobody → dann frazier (dannf) |
Changed in linux (Ubuntu Bionic): | |
status: | In Progress → Won't Fix |
Changed in linux (Ubuntu Cosmic): | |
status: | In Progress → Won't Fix |
Changed in linux (Ubuntu Xenial): | |
status: | New → Won't Fix |
description: | updated |
Changed in linux (Ubuntu Disco): | |
status: | In Progress → Fix Committed |
This change should qualify for an SRU. However, Canonical does not have the described hardware. We will need help from Huawei to test the SRU. Can Huawei commit to the following steps?
1) Test a PPA build with this fix (both 4.15 and 4.18) by 2019-03-27. Canonical can prepare this PPA.
2) After official Ubuntu kernel build, re-test both kernels to verify the fix. During the week of 2019-04-08.