| 2020-01-23 16:37:33 |
Jeff Lane |
bug |
|
|
added bug |
| 2020-01-23 16:39:00 |
Jeff Lane |
description |
This request was lost, unfortunately and so would need to be SRU'd into 5.3 for 18.04.4 to avoid customers needing to wait until August for 18.04.5 to land.
The following patches are in 5.4 and Microsemi have asked to have them pulled into 5.3 to update the SmartPQI driver that we carry.
391a24179423 scsi: smartpqi: bump version
48edb8780100 scsi: smartpqi: update copyright
63a7956ae1e8 scsi: smartpqi: add new pci ids
9946a3987248 scsi: smartpqi: correct REGNEWD return status
71ecc60d9ba4 scsi: smartpqi: add gigabyte controller
530dd8a7a2b1 scsi: smartpqi: correct hang when deleting 32 lds
2d2ad4bc724e scsi: smartpqi: add bay identifier
6d90615f1346 scsi: smartpqi: add sysfs entries
522bc026f013 scsi: smartpqi: add module param to hide vsep
8bdb3b9c67c5 scsi: smartpqi: add pci ids for fiberhome controller
5e6a9760f7da scsi: smartpqi: add module param for exposure order
All are clean cherry-picks into Eoan/master-next from 5.4 and do not touch anything outside of Microsemi's smartpqi driver. |
This request was lost, unfortunately, so I'm resubmitting and at this poing would need to be SRU'd into 5.3 for 18.04.4 to avoid customers needing to wait until August for 18.04.5 to land.
The following patches are in 5.4 and Microsemi have asked to have them pulled into 5.3 to update the SmartPQI driver that we carry.
391a24179423 scsi: smartpqi: bump version
48edb8780100 scsi: smartpqi: update copyright
63a7956ae1e8 scsi: smartpqi: add new pci ids
9946a3987248 scsi: smartpqi: correct REGNEWD return status
71ecc60d9ba4 scsi: smartpqi: add gigabyte controller
530dd8a7a2b1 scsi: smartpqi: correct hang when deleting 32 lds
2d2ad4bc724e scsi: smartpqi: add bay identifier
6d90615f1346 scsi: smartpqi: add sysfs entries
522bc026f013 scsi: smartpqi: add module param to hide vsep
8bdb3b9c67c5 scsi: smartpqi: add pci ids for fiberhome controller
5e6a9760f7da scsi: smartpqi: add module param for exposure order
All are clean cherry-picks into Eoan/master-next from 5.4 and do not touch anything outside of Microsemi's smartpqi driver.
Impact:
Most Ubuntu customers prefer the simplicity of using inbox drivers over out-of-box drivers Microsemi provides. To do that well, we should keep that inbox driver moving forward. If we don't make the updates this time, 18.04 customers would be waiting until ~ August 2020 for 18.04.5 update. |
|
| 2020-01-23 16:39:10 |
Jeff Lane |
nominated for series |
|
Ubuntu Eoan |
|
| 2020-01-23 16:39:10 |
Jeff Lane |
bug task added |
|
linux (Ubuntu Eoan) |
|
| 2020-01-23 16:45:59 |
Jeff Lane |
description |
This request was lost, unfortunately, so I'm resubmitting and at this poing would need to be SRU'd into 5.3 for 18.04.4 to avoid customers needing to wait until August for 18.04.5 to land.
The following patches are in 5.4 and Microsemi have asked to have them pulled into 5.3 to update the SmartPQI driver that we carry.
391a24179423 scsi: smartpqi: bump version
48edb8780100 scsi: smartpqi: update copyright
63a7956ae1e8 scsi: smartpqi: add new pci ids
9946a3987248 scsi: smartpqi: correct REGNEWD return status
71ecc60d9ba4 scsi: smartpqi: add gigabyte controller
530dd8a7a2b1 scsi: smartpqi: correct hang when deleting 32 lds
2d2ad4bc724e scsi: smartpqi: add bay identifier
6d90615f1346 scsi: smartpqi: add sysfs entries
522bc026f013 scsi: smartpqi: add module param to hide vsep
8bdb3b9c67c5 scsi: smartpqi: add pci ids for fiberhome controller
5e6a9760f7da scsi: smartpqi: add module param for exposure order
All are clean cherry-picks into Eoan/master-next from 5.4 and do not touch anything outside of Microsemi's smartpqi driver.
Impact:
Most Ubuntu customers prefer the simplicity of using inbox drivers over out-of-box drivers Microsemi provides. To do that well, we should keep that inbox driver moving forward. If we don't make the updates this time, 18.04 customers would be waiting until ~ August 2020 for 18.04.5 update. |
[Impact]
Most Ubuntu customers prefer the simplicity of using inbox drivers over out-of-box drivers Microsemi provides. To do that well, we should keep that inbox driver moving forward. If we don't make the updates this time, 18.04 customers would be waiting until ~ August 2020 for 18.04.5 update.
[Fixes]
The following patches are in 5.4 and Microsemi have asked to have them pulled into 5.3 to update the SmartPQI driver that we carry.
391a24179423 scsi: smartpqi: bump version
48edb8780100 scsi: smartpqi: update copyright
63a7956ae1e8 scsi: smartpqi: add new pci ids
9946a3987248 scsi: smartpqi: correct REGNEWD return status
71ecc60d9ba4 scsi: smartpqi: add gigabyte controller
530dd8a7a2b1 scsi: smartpqi: correct hang when deleting 32 lds
2d2ad4bc724e scsi: smartpqi: add bay identifier
6d90615f1346 scsi: smartpqi: add sysfs entries
522bc026f013 scsi: smartpqi: add module param to hide vsep
8bdb3b9c67c5 scsi: smartpqi: add pci ids for fiberhome controller
5e6a9760f7da scsi: smartpqi: add module param for exposure order
All are clean cherry-picks into Eoan/master-next from 5.4 and do not touch anything outside of Microsemi's smartpqi driver.
[Regression Risk]
Low, these are updates and bug fixes from the upstream maintainer and have already been tested by the upstream on Ubuntu. |
|
| 2020-01-23 17:00:09 |
Ubuntu Kernel Bot |
linux (Ubuntu): status |
New |
Incomplete |
|
| 2020-01-23 17:00:10 |
Ubuntu Kernel Bot |
linux (Ubuntu Eoan): status |
New |
Incomplete |
|
| 2020-01-23 17:01:15 |
Jeff Lane |
description |
[Impact]
Most Ubuntu customers prefer the simplicity of using inbox drivers over out-of-box drivers Microsemi provides. To do that well, we should keep that inbox driver moving forward. If we don't make the updates this time, 18.04 customers would be waiting until ~ August 2020 for 18.04.5 update.
[Fixes]
The following patches are in 5.4 and Microsemi have asked to have them pulled into 5.3 to update the SmartPQI driver that we carry.
391a24179423 scsi: smartpqi: bump version
48edb8780100 scsi: smartpqi: update copyright
63a7956ae1e8 scsi: smartpqi: add new pci ids
9946a3987248 scsi: smartpqi: correct REGNEWD return status
71ecc60d9ba4 scsi: smartpqi: add gigabyte controller
530dd8a7a2b1 scsi: smartpqi: correct hang when deleting 32 lds
2d2ad4bc724e scsi: smartpqi: add bay identifier
6d90615f1346 scsi: smartpqi: add sysfs entries
522bc026f013 scsi: smartpqi: add module param to hide vsep
8bdb3b9c67c5 scsi: smartpqi: add pci ids for fiberhome controller
5e6a9760f7da scsi: smartpqi: add module param for exposure order
All are clean cherry-picks into Eoan/master-next from 5.4 and do not touch anything outside of Microsemi's smartpqi driver.
[Regression Risk]
Low, these are updates and bug fixes from the upstream maintainer and have already been tested by the upstream on Ubuntu. |
[Impact]
Most Ubuntu customers prefer the simplicity of using inbox drivers over out-of-box drivers Microsemi provides. To do that well, we should keep that inbox driver moving forward. If we don't make the updates this time, 18.04 customers would be waiting until ~ August 2020 for 18.04.5 update.
Microsemi have asked to have them pulled into 5.3 to update the SmartPQI driver that we carry.
[Fixes]
The following patches are in 5.4 Mainline and also our Focal tree are all clean cherry picks into 5.3.
391a24179423 scsi: smartpqi: bump version
48edb8780100 scsi: smartpqi: update copyright
63a7956ae1e8 scsi: smartpqi: add new pci ids
9946a3987248 scsi: smartpqi: correct REGNEWD return status
71ecc60d9ba4 scsi: smartpqi: add gigabyte controller
530dd8a7a2b1 scsi: smartpqi: correct hang when deleting 32 lds
2d2ad4bc724e scsi: smartpqi: add bay identifier
6d90615f1346 scsi: smartpqi: add sysfs entries
522bc026f013 scsi: smartpqi: add module param to hide vsep
8bdb3b9c67c5 scsi: smartpqi: add pci ids for fiberhome controller
5e6a9760f7da scsi: smartpqi: add module param for exposure order
All are clean cherry-picks into Eoan/master-next from 5.4 and do not touch anything outside of Microsemi's smartpqi driver.
[Regression Risk]
Low, these are updates and bug fixes from the upstream maintainer and have already been tested by the upstream on Ubuntu. |
|
| 2020-01-23 17:26:43 |
Jeff Lane |
linux (Ubuntu): status |
Incomplete |
Confirmed |
|
| 2020-01-23 17:26:46 |
Jeff Lane |
linux (Ubuntu Eoan): status |
Incomplete |
Confirmed |
|
| 2020-01-23 22:16:31 |
Jeff Lane |
description |
[Impact]
Most Ubuntu customers prefer the simplicity of using inbox drivers over out-of-box drivers Microsemi provides. To do that well, we should keep that inbox driver moving forward. If we don't make the updates this time, 18.04 customers would be waiting until ~ August 2020 for 18.04.5 update.
Microsemi have asked to have them pulled into 5.3 to update the SmartPQI driver that we carry.
[Fixes]
The following patches are in 5.4 Mainline and also our Focal tree are all clean cherry picks into 5.3.
391a24179423 scsi: smartpqi: bump version
48edb8780100 scsi: smartpqi: update copyright
63a7956ae1e8 scsi: smartpqi: add new pci ids
9946a3987248 scsi: smartpqi: correct REGNEWD return status
71ecc60d9ba4 scsi: smartpqi: add gigabyte controller
530dd8a7a2b1 scsi: smartpqi: correct hang when deleting 32 lds
2d2ad4bc724e scsi: smartpqi: add bay identifier
6d90615f1346 scsi: smartpqi: add sysfs entries
522bc026f013 scsi: smartpqi: add module param to hide vsep
8bdb3b9c67c5 scsi: smartpqi: add pci ids for fiberhome controller
5e6a9760f7da scsi: smartpqi: add module param for exposure order
All are clean cherry-picks into Eoan/master-next from 5.4 and do not touch anything outside of Microsemi's smartpqi driver.
[Regression Risk]
Low, these are updates and bug fixes from the upstream maintainer and have already been tested by the upstream on Ubuntu. |
[Impact]
Most Ubuntu customers prefer the simplicity of using inbox drivers over out-of-box drivers Microsemi provides. To do that well, we should keep that inbox driver moving forward. If we don't land the updates in 18.04.4 customers would be waiting until ~ August 2020 for the 18.04.5 update.
Microsemi have asked to have them pulled into 5.3 to update the SmartPQI driver that we carry.
[Fixes]
The following patches are in 5.4 Mainline and also our Focal tree are all clean cherry picks into 5.3.
391a24179423 scsi: smartpqi: bump version
48edb8780100 scsi: smartpqi: update copyright
63a7956ae1e8 scsi: smartpqi: add new pci ids
9946a3987248 scsi: smartpqi: correct REGNEWD return status
71ecc60d9ba4 scsi: smartpqi: add gigabyte controller
530dd8a7a2b1 scsi: smartpqi: correct hang when deleting 32 lds
2d2ad4bc724e scsi: smartpqi: add bay identifier
6d90615f1346 scsi: smartpqi: add sysfs entries
522bc026f013 scsi: smartpqi: add module param to hide vsep
8bdb3b9c67c5 scsi: smartpqi: add pci ids for fiberhome controller
5e6a9760f7da scsi: smartpqi: add module param for exposure order
All are clean cherry-picks into Eoan/master-next from 5.4 and do not touch anything outside of Microsemi's smartpqi driver.
These have been cherry picked into my branch found here:
https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/eoan/+ref/1860690-smartpqi-updates-master-next
[Testing]
[Regression Risk]
Low, these are updates and bug fixes from the upstream maintainer and have already been tested by the upstream on Ubuntu. |
|
| 2020-01-23 22:56:30 |
Jeff Lane |
description |
[Impact]
Most Ubuntu customers prefer the simplicity of using inbox drivers over out-of-box drivers Microsemi provides. To do that well, we should keep that inbox driver moving forward. If we don't land the updates in 18.04.4 customers would be waiting until ~ August 2020 for the 18.04.5 update.
Microsemi have asked to have them pulled into 5.3 to update the SmartPQI driver that we carry.
[Fixes]
The following patches are in 5.4 Mainline and also our Focal tree are all clean cherry picks into 5.3.
391a24179423 scsi: smartpqi: bump version
48edb8780100 scsi: smartpqi: update copyright
63a7956ae1e8 scsi: smartpqi: add new pci ids
9946a3987248 scsi: smartpqi: correct REGNEWD return status
71ecc60d9ba4 scsi: smartpqi: add gigabyte controller
530dd8a7a2b1 scsi: smartpqi: correct hang when deleting 32 lds
2d2ad4bc724e scsi: smartpqi: add bay identifier
6d90615f1346 scsi: smartpqi: add sysfs entries
522bc026f013 scsi: smartpqi: add module param to hide vsep
8bdb3b9c67c5 scsi: smartpqi: add pci ids for fiberhome controller
5e6a9760f7da scsi: smartpqi: add module param for exposure order
All are clean cherry-picks into Eoan/master-next from 5.4 and do not touch anything outside of Microsemi's smartpqi driver.
These have been cherry picked into my branch found here:
https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/eoan/+ref/1860690-smartpqi-updates-master-next
[Testing]
[Regression Risk]
Low, these are updates and bug fixes from the upstream maintainer and have already been tested by the upstream on Ubuntu. |
[Impact]
Most Ubuntu customers prefer the simplicity of using inbox drivers over out-of-box drivers Microsemi provides. To do that well, we should keep that inbox driver moving forward. If we don't land the updates in 18.04.4 customers would be waiting until ~ August 2020 for the 18.04.5 update.
Microsemi have asked to have them pulled into 5.3 to update the SmartPQI driver that we carry.
[Fixes]
The following patches are in 5.4 Mainline and also our Focal tree are all clean cherry picks into 5.3.
391a24179423 scsi: smartpqi: bump version
48edb8780100 scsi: smartpqi: update copyright
63a7956ae1e8 scsi: smartpqi: add new pci ids
9946a3987248 scsi: smartpqi: correct REGNEWD return status
71ecc60d9ba4 scsi: smartpqi: add gigabyte controller
530dd8a7a2b1 scsi: smartpqi: correct hang when deleting 32 lds
2d2ad4bc724e scsi: smartpqi: add bay identifier
6d90615f1346 scsi: smartpqi: add sysfs entries
522bc026f013 scsi: smartpqi: add module param to hide vsep
8bdb3b9c67c5 scsi: smartpqi: add pci ids for fiberhome controller
5e6a9760f7da scsi: smartpqi: add module param for exposure order
All are clean cherry-picks into Eoan/master-next from 5.4 and do not touch anything outside of Microsemi's smartpqi driver.
These have been cherry picked into my branch found here:
https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/eoan/+ref/1860690-smartpqi-updates-master-next
[Testing]
Tested by upstream
[Regression Risk]
Low, these are updates and bug fixes from the upstream maintainer and have already been tested by the upstream on Ubuntu. |
|
| 2020-01-24 00:02:31 |
Connor Kuehl |
linux (Ubuntu Eoan): assignee |
|
Jeff Lane (bladernr) |
|
| 2020-01-24 00:02:34 |
Connor Kuehl |
linux (Ubuntu Eoan): importance |
Undecided |
Medium |
|
| 2020-01-24 00:02:36 |
Connor Kuehl |
linux (Ubuntu Eoan): status |
Confirmed |
In Progress |
|
| 2020-01-24 00:02:38 |
Connor Kuehl |
linux (Ubuntu): status |
Confirmed |
Invalid |
|
| 2020-01-24 00:03:30 |
Terry Rudd |
bug |
|
|
added subscriber Terry Rudd |
| 2020-01-24 20:32:58 |
Jeff Lane |
description |
[Impact]
Most Ubuntu customers prefer the simplicity of using inbox drivers over out-of-box drivers Microsemi provides. To do that well, we should keep that inbox driver moving forward. If we don't land the updates in 18.04.4 customers would be waiting until ~ August 2020 for the 18.04.5 update.
Microsemi have asked to have them pulled into 5.3 to update the SmartPQI driver that we carry.
[Fixes]
The following patches are in 5.4 Mainline and also our Focal tree are all clean cherry picks into 5.3.
391a24179423 scsi: smartpqi: bump version
48edb8780100 scsi: smartpqi: update copyright
63a7956ae1e8 scsi: smartpqi: add new pci ids
9946a3987248 scsi: smartpqi: correct REGNEWD return status
71ecc60d9ba4 scsi: smartpqi: add gigabyte controller
530dd8a7a2b1 scsi: smartpqi: correct hang when deleting 32 lds
2d2ad4bc724e scsi: smartpqi: add bay identifier
6d90615f1346 scsi: smartpqi: add sysfs entries
522bc026f013 scsi: smartpqi: add module param to hide vsep
8bdb3b9c67c5 scsi: smartpqi: add pci ids for fiberhome controller
5e6a9760f7da scsi: smartpqi: add module param for exposure order
All are clean cherry-picks into Eoan/master-next from 5.4 and do not touch anything outside of Microsemi's smartpqi driver.
These have been cherry picked into my branch found here:
https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/eoan/+ref/1860690-smartpqi-updates-master-next
[Testing]
Tested by upstream
[Regression Risk]
Low, these are updates and bug fixes from the upstream maintainer and have already been tested by the upstream on Ubuntu. |
[Impact]
Most Ubuntu customers prefer the simplicity of using inbox drivers over out-of-box drivers Microsemi provides. To do that well, we should keep that inbox driver moving forward. If we don't land the updates in 18.04.4 customers would be waiting until ~ August 2020 for the 18.04.5 update.
Microsemi have asked to have them pulled into 5.3 to update the SmartPQI driver that we carry.
[Fixes]
The following patches are in 5.4 Mainline and Focal.
391a24179423 scsi: smartpqi: bump version
48edb8780100 scsi: smartpqi: update copyright
63a7956ae1e8 scsi: smartpqi: add new pci ids
9946a3987248 scsi: smartpqi: correct REGNEWD return status
71ecc60d9ba4 scsi: smartpqi: add gigabyte controller
530dd8a7a2b1 scsi: smartpqi: correct hang when deleting 32 lds
2d2ad4bc724e scsi: smartpqi: add bay identifier
6d90615f1346 scsi: smartpqi: add sysfs entries
522bc026f013 scsi: smartpqi: add module param to hide vsep
8bdb3b9c67c5 scsi: smartpqi: add pci ids for fiberhome controller
5e6a9760f7da scsi: smartpqi: add module param for exposure order
All are clean cherry-picks into Eoan/master-next from 5.4 and do not touch anything outside of Microsemi's smartpqi driver.
These have been cherry picked into my branch found here:
https://code.launchpad.net/~bladernr/ubuntu/+source/linux/+git/eoan/+ref/1860690-smartpqi-updates-master-next
[Testing]
Verify via lsmod the driver is loaded
Verify via modinfo the driver version is correct (1.2.8-026)
[Regression Risk]
Low, these are updates and bug fixes from the upstream maintainer and have already been tested by the upstream on Ubuntu. |
|
| 2020-01-28 18:46:23 |
Khaled El Mously |
linux (Ubuntu Eoan): status |
In Progress |
Fix Committed |
|
| 2020-02-03 22:44:08 |
Ubuntu Kernel Bot |
tags |
|
verification-needed-eoan |
|
| 2020-02-17 10:23:38 |
Launchpad Janitor |
linux (Ubuntu Eoan): status |
Fix Committed |
Fix Released |
|
| 2020-02-17 10:23:38 |
Launchpad Janitor |
cve linked |
|
2019-19050 |
|
| 2020-02-17 10:23:38 |
Launchpad Janitor |
cve linked |
|
2019-19077 |
|
| 2020-02-17 10:23:38 |
Launchpad Janitor |
cve linked |
|
2019-19078 |
|
| 2020-02-17 10:23:38 |
Launchpad Janitor |
cve linked |
|
2019-19082 |
|
| 2020-02-17 10:23:38 |
Launchpad Janitor |
cve linked |
|
2019-19332 |
|
| 2020-02-17 10:23:38 |
Launchpad Janitor |
cve linked |
|
2019-19965 |
|
