driver/broadcom/bnxt: invalid dev_port
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
In Progress
|
Medium
|
Krzysztof Kozlowski | ||
Focal |
In Progress
|
Medium
|
Krzysztof Kozlowski |
Bug Description
[SRU Justification]
[Impact]
With broadcom dual port NIC naming convention between port 1 and port 2 can be inconsistent
For example, if network port 1 of a device is named enp1s0f0, port 2 can end up with the name enp1s0f1d1 rather than enp1s0f1
Issue is due to an inconsistent port_dev and any scripts based on it can have unexpected behavior
This has been fixed in v5.6 by the following upstream commit
- 1d86859fdf31(
https:/
The bug exists since the beginning of the driver.
== Fix ==
Backport the requested patches to Focal (5.4)
== Risk of Regression ==
The patch is trivial, the potential regressions are low.
affects: | canonical-identity-provider → linux (Ubuntu) |
no longer affects: | linux (Ubuntu Groovy) |
no longer affects: | linux (Ubuntu Hirsute) |
no longer affects: | linux (Ubuntu Impish) |
Changed in linux (Ubuntu): | |
status: | Invalid → In Progress |
Changed in linux (Ubuntu Focal): | |
importance: | Undecided → Medium |
Changed in linux (Ubuntu): | |
importance: | Undecided → Medium |
For the risk of regression - this paragraph should explain possible failures, for example if something goes wrong. Even trivial patch can cause some effects. This one as well.