| 2022-12-07 23:48:19 |
Luke Nowakowski-Krijger |
bug |
|
|
added bug |
| 2022-12-07 23:50:41 |
Luke Nowakowski-Krijger |
bug task added |
|
ubuntu |
|
| 2022-12-07 23:50:47 |
Luke Nowakowski-Krijger |
bug task deleted |
ubuntu |
|
|
| 2022-12-07 23:50:57 |
Luke Nowakowski-Krijger |
bug task added |
|
linux (Ubuntu) |
|
| 2022-12-07 23:51:06 |
Luke Nowakowski-Krijger |
nominated for series |
|
Ubuntu Kinetic |
|
| 2022-12-07 23:51:06 |
Luke Nowakowski-Krijger |
bug task added |
|
linux (Ubuntu Kinetic) |
|
| 2022-12-08 00:00:07 |
Ubuntu Kernel Bot |
linux (Ubuntu): status |
New |
Incomplete |
|
| 2022-12-08 00:00:11 |
Ubuntu Kernel Bot |
linux (Ubuntu Kinetic): status |
New |
Incomplete |
|
| 2022-12-08 00:03:32 |
Luke Nowakowski-Krijger |
linux (Ubuntu): status |
Incomplete |
Confirmed |
|
| 2022-12-08 00:04:21 |
Luke Nowakowski-Krijger |
summary |
mm:vma05 fails with '[vdso] bug not patched' on kinetic/linux 5.19.0-27.28 |
mm:vma05 in ubuntu_ltp fails with '[vdso] bug not patched' on kinetic/linux 5.19.0-27.28 |
|
| 2022-12-08 00:06:20 |
Luke Nowakowski-Krijger |
description |
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.......
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. |
|
| 2022-12-08 03:59:27 |
Po-Hsu Lin |
tags |
|
5.19 kinetic sru-20221114 ubuntu-ltp |
|
| 2022-12-15 09:39:12 |
Stefan Bader |
linux (Ubuntu Kinetic): importance |
Undecided |
High |
|
| 2022-12-15 09:39:18 |
Stefan Bader |
linux (Ubuntu Kinetic): status |
Incomplete |
Fix Committed |
|
| 2022-12-15 09:39:28 |
Stefan Bader |
linux (Ubuntu): status |
Confirmed |
Invalid |
|
| 2023-01-06 00:35:21 |
Launchpad Janitor |
linux (Ubuntu Kinetic): status |
Fix Committed |
Fix Released |
|
| 2023-01-09 22:27:17 |
Ubuntu Kernel Bot |
tags |
5.19 kinetic sru-20221114 ubuntu-ltp |
5.19 kernel-spammed-kinetic-linux-ibm kinetic sru-20221114 ubuntu-ltp verification-needed-kinetic |
|
| 2023-01-12 16:42:31 |
Ubuntu Kernel Bot |
tags |
5.19 kernel-spammed-kinetic-linux-ibm kinetic sru-20221114 ubuntu-ltp verification-needed-kinetic |
5.19 kernel-spammed-kinetic-linux-aws kernel-spammed-kinetic-linux-ibm kinetic sru-20221114 ubuntu-ltp verification-needed-kinetic |
|
| 2023-01-16 05:45:18 |
Po-Hsu Lin |
tags |
5.19 kernel-spammed-kinetic-linux-aws kernel-spammed-kinetic-linux-ibm kinetic sru-20221114 ubuntu-ltp verification-needed-kinetic |
5.19 kernel-spammed-kinetic-linux-aws kernel-spammed-kinetic-linux-ibm kinetic sru-20221114 ubuntu-ltp verification-done-kinetic |
|
| 2023-01-16 06:01:00 |
Po-Hsu Lin |
ubuntu-kernel-tests: status |
New |
Fix Released |
|
| 2023-01-17 13:33:46 |
Ubuntu Kernel Bot |
tags |
5.19 kernel-spammed-kinetic-linux-aws kernel-spammed-kinetic-linux-ibm kinetic sru-20221114 ubuntu-ltp verification-done-kinetic |
5.19 kernel-spammed-kinetic-linux-aws kernel-spammed-kinetic-linux-azure kernel-spammed-kinetic-linux-ibm kinetic sru-20221114 ubuntu-ltp verification-needed-kinetic |
|
| 2023-01-18 02:01:52 |
Po-Hsu Lin |
tags |
5.19 kernel-spammed-kinetic-linux-aws kernel-spammed-kinetic-linux-azure kernel-spammed-kinetic-linux-ibm kinetic sru-20221114 ubuntu-ltp verification-needed-kinetic |
5.19 kernel-spammed-kinetic-linux-aws kernel-spammed-kinetic-linux-azure kernel-spammed-kinetic-linux-ibm kinetic sru-20221114 ubuntu-ltp verification-done-kinetic |
|
| 2023-01-31 23:27:23 |
Ubuntu Kernel Bot |
tags |
5.19 kernel-spammed-kinetic-linux-aws kernel-spammed-kinetic-linux-azure kernel-spammed-kinetic-linux-ibm kinetic sru-20221114 ubuntu-ltp verification-done-kinetic |
5.19 kernel-spammed-jammy-linux-aws-5.19 kernel-spammed-kinetic-linux-aws kernel-spammed-kinetic-linux-azure kernel-spammed-kinetic-linux-ibm kinetic sru-20221114 ubuntu-ltp verification-done-kinetic verification-needed-jammy |
|
| 2023-01-31 23:28:02 |
Ubuntu Kernel Bot |
tags |
5.19 kernel-spammed-jammy-linux-aws-5.19 kernel-spammed-kinetic-linux-aws kernel-spammed-kinetic-linux-azure kernel-spammed-kinetic-linux-ibm kinetic sru-20221114 ubuntu-ltp verification-done-kinetic verification-needed-jammy |
5.19 kernel-spammed-jammy-linux-aws-5.19 kernel-spammed-jammy-linux-lowlatency-hwe-5.19 kernel-spammed-kinetic-linux-aws kernel-spammed-kinetic-linux-azure kernel-spammed-kinetic-linux-ibm kinetic sru-20221114 ubuntu-ltp verification-done-kinetic verification-needed-jammy |
|
| 2023-07-30 15:10:25 |
wangying |
bug |
|
|
added subscriber wangying |
