test_too_early_vsyscall in ubuntu_qrt_kernel_panic failed on N-gcp N2D instances (Exec format error)

[Po-Hsu Lin]

Issue found on 6.8.0-1008.9 in sru-20240429

Test failed with Google N2D instances only, test output:
FAIL: test_too_early_vsyscall (__main__.KernelPanicTest.test_too_early_vsyscall)
 The vsyscall entries are created too early (CVE-2010-0307)
 ----------------------------------------------------------------------
 Traceback (most recent call last):
   File "/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_panic/src/qa-regression-testing/scripts/./test-kernel-panic.py", line 78, in test_too_early_vsyscall
     self.assertShellExitEquals(0, ["make", 'test'])
   File "/home/ubuntu/autotest/client/tmp/ubuntu_qrt_kernel_panic/src/qa-regression-testing/scripts/testlib.py", line 1331, in assertShellExitEquals
     self.assertEqual(expected, rc, msg + result + report)
 AssertionError: 0 != 2 : Got exit code 2, expected 0
 Command: 'make', 'test'
 Output:
 gcc -m32 -o amd64_killer amd64_killer.c
 gcc -m64 -Wl,--dynamic-linker,/non-existent.so -o poison amd64_killer.c
 ulimit -c 1024 ; ./amd64_killer ./poison ; ret=$? ; if [ $ret -eq 139 ]; then echo correctly segfaulted instead of panic; exit 0; else echo did not segfault?; exit 1; fi
 /bin/bash: line 1: ./amd64_killer: cannot execute binary file: Exec format error
 did not segfault?
 make: *** [Makefile:6: test] Error 1

[Po-Hsu Lin (cypressyew)]

This is because of the 32bit support was disabled on Google N2D confidential computing VMs. See bug 2072457