test_078_SLAB_freelist_randomization from ubuntu_qrt_kernel_security failed on Trusty 3.13

[Po-Hsu Lin]

This test case does not exist before 3.13.0-125, therefore no history to check with.

FAIL: test_078_SLAB_freelist_randomization (__main__.KernelSecurityTest)
Ensure CONFIG_SLAB_FREELIST_RANDOM is set
----------------------------------------------------------------------
Traceback (most recent call last):
File "./test-kernel-security.py", line 899, in test_078_SLAB_freelist_randomization
self.assertTrue(self._test_config('SLAB_FREELIST_RANDOM'), )
AssertionError: False is not true

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1704062

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Po-Hsu Lin (cypressyew)]

Tested on 3.13.0-123-generic #172 with node fozzie

test_078_SLAB_freelist_randomization (__main__.KernelSecurityTest)
Ensure CONFIG_SLAB_FREELIST_RANDOM is set ... (skipped: CONFIG_SLAB_FREELIST_RANDOM enabled in linux v4.8) ok

And it passed with 3.13.0-125 in -proposed on the very same node:
test_078_SLAB_freelist_randomization (__main__.KernelSecurityTest)
Ensure CONFIG_SLAB_FREELIST_RANDOM is set ... (skipped: CONFIG_SLAB_FREELIST_RANDOM enabled in linux v4.8) ok

I will restart the one failed on the jenkins server.

[Po-Hsu Lin (cypressyew)]

Tested again on the node from our jenkins server, it has passed the test.
Looks like a test case issue.

Therefore I will mark this one as Invalid.
Thanks

[Steve Beattie (sbeattie)]

Yes, sorry, I added the test to ensure that slab freelist randomization was enabled in our 4.8 kernels and later (it didn't exist upstream before then), but inverted the logic around the version test accidentally. I'd already fixed it, thus later test runs got the corrected test case and thus didn't fail. Sorry about that!