After chatting with xnox on IRC, he discovered that the output of catting /proc/modules in 4.15 now depends on who is doing the catting.
So `cat /proc/modules` as a normal user will return null references while `sudo cat /proc/modules` will return the actual memory offsets, accurately.
For example: ubuntu@xwing:~$ sudo cat /proc/modules |grep e1000e e1000e 249856 0 - Live 0xffffffffc0225000 ptp 20480 2 igb,e1000e, Live 0xffffffffc00a9000 ubuntu@xwing:~$ cat /proc/modules |grep e1000e e1000e 249856 0 - Live 0x (null) ptp 20480 2 igb,e1000e, Live 0x (null)
So for the cert tooling, this should be a simple fix then, just to ensure that the module script runs as root.
After chatting with xnox on IRC, he discovered that the output of catting /proc/modules in 4.15 now depends on who is doing the catting.
So `cat /proc/modules` as a normal user will return null references while `sudo cat /proc/modules` will return the actual memory offsets, accurately.
For example:
ubuntu@xwing:~$ sudo cat /proc/modules |grep e1000e
e1000e 249856 0 - Live 0xffffffffc0225000
ptp 20480 2 igb,e1000e, Live 0xffffffffc00a9000
ubuntu@xwing:~$ cat /proc/modules |grep e1000e
e1000e 249856 0 - Live 0x (null)
ptp 20480 2 igb,e1000e, Live 0x (null)
So for the cert tooling, this should be a simple fix then, just to ensure that the module script runs as root.