TC filters are broken on Mellanox after upstream stable updates
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Bionic |
Fix Released
|
Undecided
|
Juerg Haefliger |
Bug Description
[Impact]
Mellanox TC filters don't work for some key rules after the Bionic 4.15 stable patchset 2019-07-12 update (LP: #1836426). The offending commit is ("net/mlx5e: Set vlan masks for all offloaded TC rules").
This causes fatal network connectivity issues for projects that use the Mellanox ConnectX 5 NIC.
[Test Case]
TBD.
[Fix]
Backport the following upstream commit (which fixes the offending commit) and its prerequisites:
d3a80bb5a3ea ("net/mlx5e: Don't match on vlan non-existence if ethertype is wildcarded")
[Regression Potential]
Low. Changes are isolated and limited to the mlx5_core driver and all commits are in upstream stable v4.19.y.
[Original description]
The following upstream fix was missing from the latest upstream stable update (LP: # and LP1839376: #1839213):
CVE References
summary: |
- TC filters are broken on Mellanox with kernels -1030 and greater + TC filters are broken on Mellanox after upstream stable updates |
description: | updated |
Changed in linux (Ubuntu Bionic): | |
status: | New → In Progress |
assignee: | nobody → Marcelo Cerri (mhcerri) |
tags: | added: sts |
Changed in linux (Ubuntu Bionic): | |
assignee: | Marcelo Cerri (mhcerri) → Juerg Haefliger (juergh) |
description: | updated |
Changed in linux (Ubuntu Bionic): | |
status: | In Progress → Fix Committed |
tags: |
added: verification-done-bionic removed: verification-needed-bionic |
Changed in linux (Ubuntu): | |
status: | Incomplete → Invalid |
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
apport-collect 1842502
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the Ubuntu Kernel Team.