Comment 2 for bug 1953366

Revision history for this message
Thadeu Lima de Souza Cascardo (cascardo) wrote :

As this is failing on ADT, it is failing on VMs on an environment we don't have much control of. This could be caused by host kernel, qemu or libvirt combinations that will make the guest kernel observe a given mitigation while it's not really in place.

This test was added after 5.4, so the failure won't be observed on kernels before 5.11. I have fixed it once so it detects the Vulnerable case and have the test return the SKIP code.

We need to fix this sooner rather than later, otherwise ADT test results will continue to fail. The other option is to skip this on our tests.

Cascardo.