kselftest net/fib_nexthop_nongw.sh fails
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux-kvm (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Jammy |
Fix Released
|
Undecided
|
Unassigned | ||
Kinetic |
Fix Released
|
Undecided
|
Unassigned | ||
Lunar |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
18272 03:33:07 DEBUG| Persistent state client.
18273 03:33:07 DEBUG| Persistent state client.
18274 03:33:07 DEBUG| Waiting for pid 58525 for 2700 seconds
18275 03:33:07 WARNI| System python is too old, crash handling disabled
18276 03:33:07 DEBUG| Running 'make run_tests -C net TEST_PROGS=
18277 03:33:07 DEBUG| [stdout] make: Entering directory '/home/
18278 03:33:07 DEBUG| [stdout] make --no-builtin-rules ARCH=x86 -C ../../../.. headers_install
18279 03:33:07 DEBUG| [stdout] make[1]: Entering directory '/home/
18280 03:33:08 DEBUG| [stdout] INSTALL ./usr/include
18281 03:33:08 DEBUG| [stdout] make[1]: Leaving directory '/home/
18282 03:33:08 DEBUG| [stdout] TAP version 13
18283 03:33:08 DEBUG| [stdout] 1..1
18284 03:33:08 DEBUG| [stdout] # selftests: net: fib_nexthop_
18285 03:33:08 DEBUG| [stdout] # Error: Unknown device type.
18286 03:33:08 DEBUG| [stdout] # Cannot find device "eth0"
18287 03:33:08 DEBUG| [stdout] # Cannot find device "eth0"
18288 03:33:08 DEBUG| [stdout] # TEST: nexthop: get route with nexthop without gw [ OK ]
18289 03:33:18 DEBUG| [stdout] # TEST: nexthop: ping through nexthop without gw [FAIL]
18290 03:33:18 DEBUG| [stdout] not ok 1 selftests: net: fib_nexthop_
18291 03:33:18 DEBUG| [stdout] make: Leaving directory '/home/
-------
SRU Justification:
[Impact]
* Without Kernel support for the Dummy net driver, it is not possible to successfully run selftests that use it. This includes as per this bug net/fib_
[Fix]
* Custom patch to enable CONFIG_DUMMY=m
[Test Plan]
* Before the fix, the net/fib_
$ ip -n h1 link add name eth0 type dummy
Error: Unknown device type.
After the fix it does not fail.
[Where problems could occur]
* The regression can be considered as low, since we are adding functionality not previously present.
[Other Info]
* There does not seem to be a historical reason for removing it from linux-kvm.
CVE References
summary: |
- fib_nexthop_nongw.sh + kselftest net/fib_nexthop_nongw.sh fails |
description: | updated |
Changed in linux-kvm (Ubuntu Lunar): | |
status: | New → Confirmed |
Changed in linux-kvm (Ubuntu Kinetic): | |
status: | New → Confirmed |
Changed in linux-kvm (Ubuntu Jammy): | |
status: | New → Confirmed |
Changed in linux-kvm (Ubuntu Jammy): | |
status: | Confirmed → Fix Committed |
Changed in linux-kvm (Ubuntu Kinetic): | |
status: | Confirmed → Fix Committed |
Hello!
I have investigated further on this bug.
It is failing because the kernel does not contain dummy net driver. Then adding a dummy interface fails.
Command:
$ ip -n h1 link add name eth0 type dummy
Error: Unknown device type.
Module missing (From generic example):
/lib/modules/ 5.15.0- 57-generic/ kernel/ drivers/ net/dummy. ko
Do we want to make an equivalent test, or include the module? I would say the latter.