canonical-ubuntu-qa team mailing list archive

[Koichiro Den <2036959@xxxxxxxxxxxxxxxxxx>]

Similar issue found on J-hwe-6.8-6.8.0-50.51~22.04.1 (2024.10.28).
Note that the test code has been modified a lot (e.g. 6469b66e3f5a ("selftests: improve vm.memfd_noexec sysctl tests"))


03:53:48 DEBUG| [stdout] # selftests: memfd: memfd_test
03:53:48 DEBUG| [stdout] # memfd: CREATE
03:53:48 DEBUG| [stdout] # memfd: BASIC
03:53:48 DEBUG| [stdout] # memfd: SEAL-EXEC
03:53:48 DEBUG| [stdout] # memfd:	Apply SEAL_EXEC
03:53:48 DEBUG| [stdout] # memfd:	Apply ALL_SEALS
03:53:48 DEBUG| [stdout] # memfd: EXEC_NO_SEAL
03:53:48 DEBUG| [stdout] # memfd: NOEXEC_SEAL
03:53:48 DEBUG| [stdout] # memfd: SEAL-WRITE
03:53:48 DEBUG| [stdout] # memfd: SEAL-FUTURE-WRITE
03:53:48 DEBUG| [stdout] # memfd: SEAL-SHRINK
03:53:48 DEBUG| [stdout] # memfd: SEAL-GROW
03:53:48 DEBUG| [stdout] # memfd: SEAL-RESIZE
03:53:48 DEBUG| [stdout] # memfd: sysctl 0
03:53:48 DEBUG| [stdout] # memfd: sysctl 1
03:53:48 DEBUG| [stdout] # memfd: sysctl 0
03:53:48 DEBUG| [stdout] # memfd: sysctl 2
03:53:48 DEBUG| [stdout] # memfd: sysctl 1
03:53:48 DEBUG| [stdout] # memfd: sysctl 0
03:53:48 DEBUG| [stdout] # memfd: nested sysctl 0
03:53:48 DEBUG| [stdout] # memfd: sysctl 0
03:53:48 DEBUG| [stdout] # memfd: sysctl 1
03:53:48 DEBUG| [stdout] # memfd: sysctl 0
03:53:48 DEBUG| [stdout] # memfd: sysctl 2
03:53:48 DEBUG| [stdout] # memfd: sysctl 1
03:53:48 DEBUG| [stdout] # memfd: sysctl 0
03:53:48 DEBUG| [stdout] # memfd: nested sysctl 1
03:53:48 DEBUG| [stdout] # memfd: nested sysctl 2
03:53:48 DEBUG| [stdout] # memfd: nested sysctl 0 -> 1 after fork
03:53:48 DEBUG| [stdout] # write sysctl 0 succeeded, but failure expected
03:53:48 DEBUG| [stdout] # newpid thread: killed by signal 5
03:53:49 DEBUG| [stdout] # newpid thread: killed by signal 5
03:53:49 DEBUG| [stdout] # /usr/bin/timeout: the monitored command dumped core
03:53:49 DEBUG| [stdout] # Aborted
03:53:49 DEBUG| [stdout] not ok 1 selftests: memfd: memfd_test # exit=134

-- 
You received this bug notification because you are a member of Canonical
Platform QA Team, which is subscribed to ubuntu-kernel-tests.
https://bugs.launchpad.net/bugs/2036959

Title:
  memfd_test from ubuntu_kernel_selftests failed with J-oem-6.5

Status in ubuntu-kernel-tests:
  New

Bug description:
  Issue found with J-oem-6.5.0-1004.4

  This issue does not exist with -1003, but after comparing the test
  output. It looks like there is a new test case "memfd: sysctl" added
  in -1004.

  Test failed with:
  $ sudo ./memfd_test
  memfd: CREATE
  memfd: BASIC
  memfd: SEAL-EXEC
  memfd:	Apply SEAL_EXEC
  memfd:	Apply ALL_SEALS
  memfd: EXEC_NO_SEAL
  memfd: NOEXEC_SEAL
  memfd: SEAL-WRITE
  memfd: SEAL-FUTURE-WRITE
  memfd: SEAL-SHRINK
  memfd: SEAL-GROW
  memfd: SEAL-RESIZE
  memfd: SHARE-DUP
  memfd: SHARE-MMAP
  memfd: SHARE-OPEN
  memfd: SHARE-FORK
  memfd: SHARE-DUP (shared file-table)
  memfd: SHARE-MMAP (shared file-table)
  memfd: SHARE-OPEN (shared file-table)
  memfd: SHARE-FORK (shared file-table)
  memfd: sysctl 0
  memfd: sysctl 1
  memfd: child ns
  write sysctl 0 succeeded, but failure expected
  newpid thread: killed by signal 11
  Aborted

  In dmesg you will see:
  [13767.435614] traps: memfd_test[355397] general protection fault ip:7f5aef428898 sp:560eb3872570 error:0 in libc.so.6[7f5aef428000+195000]

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