[Impact]
We don't want sosreport to triger kernel module to load. This is causing Bionic autopkgtest to fails on 4.15 kernel.
simple.sh will report a failure: "new kernel modules loaded during execution"
[Test case]
On a 4.15 kernel (Bionic)
root@srv:~# lsmod | grep -i devlink root@srv:~# sos report -o networking root@srv:~# lsmod | grep -i devlink devlink 45056 0
Not reproducible on Bionic w/ 5.4 kernel for instance
Reason: config-4.15.0-140-generic:CONFIG_MAY_USE_DEVLINK=m config-5.4.0-70-generic:CONFIG_NET_DEVLINK=y
CONFIG_MAY_USE_DEVLINK: Drivers using the devlink infrastructure should have a dependency on MAY_USE_DEVLINK to ensure they do not cause link errors when devlink is a loadable module and the driver using it is built-in.
[Where problem could occur]
[Other information]
Upstream issues: https://github.com/sosreport/sos/issues/2468
[Impact]
We don't want sosreport to triger kernel module to load.
This is causing Bionic autopkgtest to fails on 4.15 kernel.
simple.sh will report a failure:
"new kernel modules loaded during execution"
[Test case]
On a 4.15 kernel (Bionic)
root@srv:~# lsmod | grep -i devlink
root@srv:~# sos report -o networking
root@srv:~# lsmod | grep -i devlink
devlink 45056 0
Not reproducible on Bionic w/ 5.4 kernel for instance
Reason: 4.15.0- 140-generic: CONFIG_ MAY_USE_ DEVLINK= m 5.4.0-70- generic: CONFIG_ NET_DEVLINK= y
config-
config-
CONFIG_ MAY_USE_ DEVLINK:
Drivers using the devlink infrastructure should have a dependency on MAY_USE_DEVLINK to ensure they do not cause link errors when devlink is a loadable module and the driver using it is built-in.
[Where problem could occur]
[Other information]
Upstream issues: /github. com/sosreport/ sos/issues/ 2468
https:/