Confirmed that this commit

commit ec95f3b24425429ccce89ed6ee35bb318de029fa
Author: Al Viro <v...@zeniv.linux.org.uk>
Date:   Mon Oct 3 20:26:08 2022 -0400

    fix coredump breakage
    
    Let me count the ways in which I'd screwed up:
    
    * when emitting a page, handling of gaps in coredump should happen
    before fetching the current file position.
    * fix for a problem that occurs on rather uncommon setups (and hadn't
    been observed in the wild) had been sent very late in the cycle.
    * ... with badly insufficient testing, introducing an easily
    reproducible breakage.  Without giving it time to soak in -next.
    
    Fucked-up-by: Al Viro <v...@zeniv.linux.org.uk>
    Reported-by: "J. R. Okajima" <hooanon...@gmail.com>
    Tested-by: "J. R. Okajima" <hooanon...@gmail.com>
    Fixes: 06bbaa6dc53c "[coredump] don't use __kernel_write() on 
kmap_local_page()"
    Cc: sta...@kernel.org   # v6.0-only
    Signed-off-by: Al Viro <v...@zeniv.linux.org.uk>

Fixes the issue.

This issue does not only affect vDSO vma's as the original test case was
suggesting, but seems to  completely breaks coredump debugging in gdb.
Probably worth a respin as this is a very user visible issue.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1999094

Title:
  mm:vma05 in ubuntu_ltp fails with '[vdso] bug not patched' on
  kinetic/linux 5.19.0-27.28

Status in ubuntu-kernel-tests:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in linux source package in Kinetic:
  Incomplete

Bug 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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1999094/+subscriptions


-- 
Mailing list: https://launchpad.net/~kernel-packages
Post to     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to