This test fails on 5.19.0-27.28 in cycle 2022.11.14 on most if not all instances.
Running tests.......
vma05 1 TINFO: timeout per run is 0h 5m 0s
vma05 1 TFAIL: [vdso] bug not patched
vma05 2 TINFO: AppArmor enabled, this may affect test results
vma05 2 TINFO: it can be disabled with TST_DISABLE_APPARMOR=1 (requires super/root)
vma05 2 TINFO: loaded AppArmor profiles: none
Looking at the contents of the triggered backtrace, on 5.19.0-26 the contents look like this:
vma05 1 TPASS: [vsyscall] reported correctly
vma05 1 TINFO: TRACE=Reading symbols from vma05_vdso...
[New LWP 418325]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `vma05_vdso'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 __pthread_kill_implementation (no_tid=0, signo=11,
threadid=<optimized out>) at ./nptl/pthread_kill.c:44
Thread 1 (Thread 0x7f3093c4e740 (LWP 418325)):
#0 __pthread_kill_implementation (no_tid=0, signo=11, threadid=<optimized out>) at ./nptl/pthread_kill.c:44
#1 __pthread_kill_internal (signo=11, threadid=<optimized out>) at ./nptl/pthread_kill.c:78
#2 __GI___pthread_kill (threadid=<optimized out>, signo=signo@entry=11) at ./nptl/pthread_kill.c:89
#3 0x00007f3093a3bc46 in __GI_raise (sig=sig@entry=11) at ../sysdeps/posix/raise.c:26
#4 0x000055f54287a072 in main () at vma05_vdso.c:5
vma05 1 TPASS: [vdso] backtrace complete
while on 5.19.0-27.28 it looks like this:
vma05 1 TINFO: TRACE=Reading symbols from vma05_vdso...
[New LWP 1501]
Core was generated by `vma05_vdso'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x00007f9b3c09226b in ?? ()
Thread 1 (LWP 1501):
#0 0x00007f9b3c09226b in ?? ()
Backtrace stopped: Cannot access memory at address 0x7ffc216242b0
vma05 1 TFAIL: [vdso] bug not patched
vma05 2 TINFO: AppArmor enabled, this may affect test results
vma05 2 TINFO: it can be disabled with TST_DISABLE_APPARMOR=1 (requires super/root)
vma05 2 TINFO: loaded AppArmor profiles: none
Suggesting that this bug has somehow been reintroduced. Will look into this further.
This test fails on 5.19.0-27.28 in cycle 2022.11.14 on most if not all instances.
Running tests....... APPARMOR= 1 (requires super/root)
vma05 1 TINFO: timeout per run is 0h 5m 0s
vma05 1 TFAIL: [vdso] bug not patched
vma05 2 TINFO: AppArmor enabled, this may affect test results
vma05 2 TINFO: it can be disabled with TST_DISABLE_
vma05 2 TINFO: loaded AppArmor profiles: none
Looking at the contents of the triggered backtrace, on 5.19.0-26 the contents look like this:
vma05 1 TPASS: [vsyscall] reported correctly 64-linux- gnu/libthread_ db.so.1" . kill_implementa tion (no_tid=0, signo=11, <optimized out>) at ./nptl/ pthread_ kill.c: 44
vma05 1 TINFO: TRACE=Reading symbols from vma05_vdso...
[New LWP 418325]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_
Core was generated by `vma05_vdso'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 __pthread_
threadid=
Thread 1 (Thread 0x7f3093c4e740 (LWP 418325)): kill_implementa tion (no_tid=0, signo=11, threadid=<optimized out>) at ./nptl/ pthread_ kill.c: 44 kill_internal (signo=11, threadid=<optimized out>) at ./nptl/ pthread_ kill.c: 78 <optimized out>, signo=signo@ entry=11) at ./nptl/ pthread_ kill.c: 89 posix/raise. c:26
#0 __pthread_
#1 __pthread_
#2 __GI___pthread_kill (threadid=
#3 0x00007f3093a3bc46 in __GI_raise (sig=sig@entry=11) at ../sysdeps/
#4 0x000055f54287a072 in main () at vma05_vdso.c:5
vma05 1 TPASS: [vdso] backtrace complete
while on 5.19.0-27.28 it looks like this:
vma05 1 TINFO: TRACE=Reading symbols from vma05_vdso...
[New LWP 1501]
Core was generated by `vma05_vdso'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x00007f9b3c09226b in ?? ()
Thread 1 (LWP 1501): APPARMOR= 1 (requires super/root)
#0 0x00007f9b3c09226b in ?? ()
Backtrace stopped: Cannot access memory at address 0x7ffc216242b0
vma05 1 TFAIL: [vdso] bug not patched
vma05 2 TINFO: AppArmor enabled, this may affect test results
vma05 2 TINFO: it can be disabled with TST_DISABLE_
vma05 2 TINFO: loaded AppArmor profiles: none
Suggesting that this bug has somehow been reintroduced. Will look into this further.