For the sake of completeness on this one, I installed the following mainline packages on an AWS m5.large instance running 16.04.3 w/ 4.4.0-112-generic
- linux-headers-4.16.0-041600rc4_4.16.0-041600rc4.201803041930_all.deb - linux-headers-4.16.0-041600rc4-generic_4.16.0-041600rc4.201803041930_amd64.deb - linux-image-4.16.0-041600rc4-generic_4.16.0-041600rc4.201803041930_amd64.deb
This does NOT trigger the bug, either via `sysctl -a` or `sysctl kernel.ibrs_dump` as `/proc/sys/kernel/ibrs_dump` does not exist. This is the same behavior on Bionic w/ 4.15.
For the sake of completeness on this one, I installed the following mainline packages on an AWS m5.large instance running 16.04.3 w/ 4.4.0-112-generic
- linux-headers- 4.16.0- 041600rc4_ 4.16.0- 041600rc4. 201803041930_ all.deb 4.16.0- 041600rc4- generic_ 4.16.0- 041600rc4. 201803041930_ amd64.deb 4.16.0- 041600rc4- generic_ 4.16.0- 041600rc4. 201803041930_ amd64.deb
- linux-headers-
- linux-image-
This does NOT trigger the bug, either via `sysctl -a` or `sysctl kernel.ibrs_dump` as `/proc/ sys/kernel/ ibrs_dump` does not exist. This is the same behavior on Bionic w/ 4.15.