[SRU] Ice driver causes the kernel to crash with Ubuntu 20.04.2 with ethtool specific register commands
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Focal |
Fix Released
|
High
|
Unassigned |
Bug Description
[Impact]
When we run the command, ethtool -d <interface_name> with Intel cards (ice driver), the kernel crashes because of the ice driver.
The same works fine with HWE kernel (5.11). Here, we do not see any crash.
[FIXES]
ice: Fix bad register reads
The "ethtool -d" handler reads registers in the ice_regs_dump_list array
and returns read values back to the userspace.
commitID: 1fba4a8a92706c8
[TESTING]
Install Focal on a system with an E810 network device.
Ensure the network device has an IP address and has connectivity
Run ethtool -d <interface_name>
Expected result: Prints a register dump for the specified network device
[REGRESSION RISK]
The regression risk is low
[OTHER INFO]
I have added the fix, built the kernel and tested the fix.
https:/
affects: | ubuntu-terminal-app → dellserver |
information type: | Private Security → Private |
information type: | Private → Public |
summary: |
- ice driver causes the kernel to crash with Ubuntu 20.04.2 with ethtool - specific register commands + [SRU] Ice driver causes the kernel to crash with Ubuntu 20.04.2 with + ethtool specific register commands |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
Changed in linux (Ubuntu Focal): | |
importance: | Undecided → High |
status: | New → In Progress |
Changed in linux (Ubuntu): | |
status: | Incomplete → Invalid |
Changed in linux (Ubuntu Focal): | |
status: | In Progress → Fix Committed |
no longer affects: | focal (Ubuntu) |
no longer affects: | focal (Ubuntu Focal) |
affects: | dellserver → ubuntu-translations |
no longer affects: | ubuntu-translations |
Changed in linux (Ubuntu): | |
status: | Invalid → Fix Released |
importance: | Undecided → High |
I was unable to open the logs in comment #1 but I did recreate the issue and I am attaching a log.