ubuntu-kernel-tests

seccomp in ubuntu_kernel_selftest failed on X/B/C s390x KVM

Bug #1809630 reported by Po-Hsu Lin on 2018-12-24

This bug affects 1 person

	Status	Importance	Assigned to
ubuntu-kernel-tests	Triaged	Undecided	Unassigned
linux (Ubuntu)	Incomplete	Undecided	Unassigned
Xenial	New	Undecided	Unassigned
Bionic	New	Undecided	Unassigned
Cosmic	Won't Fix	Undecided	Unassigned

Bug Description

There are 7 test cases failed in secomp_bpf test, and this can be reproduced with test suites from the upstream:

[ RUN ] TRACE_syscall.ptrace_syscall_dropped
TRACE_syscall.ptrace_syscall_dropped: Test failed at step #159
[ FAIL ] TRACE_syscall.ptrace_syscall_dropped

[ RUN ] TRACE_syscall.syscall_dropped
TRACE_syscall.syscall_dropped: Test failed at step #2
[ FAIL ] TRACE_syscall.syscall_dropped

[ RUN ] TRACE_syscall.skip_after_RET_TRACE
seccomp_bpf.c:1884:TRACE_syscall.skip_after_RET_TRACE:Expected -1 (18446744073709551615) == syscall(20) (14184)
seccomp_bpf.c:1885:TRACE_syscall.skip_after_RET_TRACE:Expected 1 (1) == (*__errno_location ()) (0)
TRACE_syscall.skip_after_RET_TRACE: Test failed at step #12
[ FAIL ] TRACE_syscall.skip_after_RET_TRACE

[ RUN ] TRACE_syscall.kill_after_RET_TRACE
TRACE_syscall.kill_after_RET_TRACE: Test exited normally instead of by signal (code: 0)
[ FAIL ] TRACE_syscall.kill_after_RET_TRACE

[ RUN ] TRACE_syscall.skip_after_ptrace
seccomp_bpf.c:1946:TRACE_syscall.skip_after_ptrace:Expected -1 (18446744073709551615) == syscall(20) (14184)
seccomp_bpf.c:1947:TRACE_syscall.skip_after_ptrace:Expected 1 (1) == (*__errno_location ()) (0)
TRACE_syscall.skip_after_ptrace: Test failed at step #15
[ FAIL ] TRACE_syscall.skip_after_ptrace

[ RUN ] TRACE_syscall.kill_after_ptrace
TRACE_syscall.kill_after_ptrace: Test exited normally instead of by signal (code: 0)
[ FAIL ] TRACE_syscall.kill_after_ptrace

[ RUN ] global.get_metadata
seccomp_bpf.c:2913:global.get_metadata:Expected sizeof(md) (16) == ptrace(0x420d, pid, sizeof(md), &md) (18446744073709551615)
global.get_metadata: Test terminated by assertion
[ FAIL ] global.get_metadata

Please find the complete test report here:
https://pastebin.ubuntu.com/p/tfmVypShtX/

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-43-generic 4.15.0-43.46
ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
Uname: Linux 4.15.0-43-generic s390x
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: s390x
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord'
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found.
Date: Mon Dec 24 03:33:04 2018
HibernationDevice: RESUME=UUID=caaee9b2-6bc1-4c8e-b26c-69038c092091
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
Lspci:

Lsusb: Error: command ['lsusb'] failed with exit code 1:
PciMultimedia:

ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb'
ProcKernelCmdLine: root=UUID=c7d7bbcb-a039-4ead-abfe-7672dea0add4 crashkernel=196M
RelatedPackageVersions:
linux-restricted-modules-4.15.0-43-generic N/A
linux-backports-modules-4.15.0-43-generic N/A
linux-firmware 1.173.3
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)

Tags:

Revision history for this message

Po-Hsu Lin (cypressyew) wrote on 2018-12-24:

AudioDevicesInUse.txt Edit (1.3 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (28.6 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (2.2 KiB, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (1.2 KiB, text/plain; charset="utf-8")
ProcCpuinfoMinimal.txt Edit (1.2 KiB, text/plain; charset="utf-8")
ProcEnviron.txt Edit (270 bytes, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (1.6 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (6.1 KiB, text/plain; charset="utf-8")
UdevDb.txt Edit (17.1 KiB, text/plain; charset="utf-8")
WifiSyslog.txt Edit (174.1 KiB, text/plain; charset="utf-8")

Revision history for this message

Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote on 2018-12-24: Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1809630

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status:	New → Incomplete

Revision history for this message

Po-Hsu Lin (cypressyew) wrote on 2018-12-25: Re: seccomp in ubuntu_kernel_selftest failed on B s390x KVM

Download full text (3.6 KiB)

With Cosmic s390x KVM, 6 failures reported in our source tree and in the upstream source tree:
[ RUN ] TRACE_syscall.ptrace_syscall_dropped
TRACE_syscall.ptrace_syscall_dropped: Test failed at step #127
[ FAIL ] TRACE_syscall.ptrace_syscall_dropped
[ RUN ] TRACE_syscall.syscall_dropped
TRACE_syscall.syscall_dropped: Test failed at step #2
[ FAIL ] TRACE_syscall.syscall_dropped
[ RUN ] TRACE_syscall.skip_after_RET_TRACE
seccomp_bpf.c:1884:TRACE_syscall.skip_after_RET_TRACE:Expected -1 (18446744073709551615) == syscall(20) (728)
seccomp_bpf.c:1885:TRACE_syscall.skip_after_RET_TRACE:Expected 1 (1) == (*__errno_location ()) (0)
TRACE_syscall.skip_after_RET_TRACE: Test failed at step #12
[ FAIL ] TRACE_syscall.skip_after_RET_TRACE
[ RUN ] TRACE_syscall.kill_after_RET_TRACE
TRACE_syscall.kill_after_RET_TRACE: Test exited normally instead of by signal (code: 0)
[ FAIL ] TRACE_syscall.kill_after_RET_TRACE
[ RUN ] TRACE_syscall.skip_after_ptrace
seccomp_bpf.c:1946:TRACE_syscall.skip_after_ptrace:Expected -1 (18446744073709551615) == syscall(20) (728)
seccomp_bpf.c:1947:TRACE_syscall.skip_after_ptrace:Expected 1 (1) == (*__errno_location ()) (0)
TRACE_syscall.skip_after_ptrace: Test failed at step #15
[ FAIL ] TRACE_syscall.skip_after_ptrace
[ RUN ] TRACE_syscall.kill_after_ptrace
TRACE_syscall.kill_after_ptrace: Test exited normally instead of by signal (code: 0)
[ FAIL ] TRACE_syscall.kill_after_ptrace

With Xenail s390x KVM, the test suite is outdated and it will pass with 54 tests there. With the upstream source tree, there will be 8 failures:
[ RUN ] global.KILL_process
seccomp_bpf.c:727:global.KILL_process:Expected 0 (0) != (((signed char) ((((__extension__ (((union { __typeof(status) __in; int __i; }) { .__in = (status) }).__i))) & 0x7f) + 1) >> 1) > 0) (0)
global.KILL_process: Test terminated by assertion
[ FAIL ] global.KILL_process
[ RUN ] TRACE_syscall.ptrace_syscall_dropped
TRACE_syscall.ptrace_syscall_dropped: Test failed at step #223
[ FAIL ] TRACE_syscall.ptrace_syscall_dropped
[ RUN ] TRACE_syscall.syscall_dropped
TRACE_syscall.syscall_dropped: Test failed at step #2
[ FAIL ] TRACE_syscall.syscall_dropped
[ RUN ] TRACE_syscall.skip_after_RET_TRACE
seccomp_bpf.c:1884:TRACE_syscall.skip_after_RET_TRACE:Expected -1 (18446744073709551615) == syscall(20) (5486)
seccomp_bpf.c:1885:TRACE_syscall.skip_after_RET_TRACE:Expected 1 (1) == (*__errno_location ()) (0)
TRACE_syscall.skip_after_RET_TRACE: Test failed at step #12
[ FAIL ] TRACE_syscall.skip_after_RET_TRACE
[ RUN ] TRACE_syscall.kill_after_RET_TRACE
TRACE_syscall.kill_after_RET_TRACE: Test exited normally instead of by signal (code: 0)
[ FAIL ] TRACE_syscall.kill_after_RET_TRACE
[ RUN ] TRACE_syscall.skip_after_ptrace
seccomp_bpf.c:1946:TRACE_syscall.skip_after_ptrace:Expected -1 (18446744073709551615) == syscall(20) (5486)
seccomp_bpf.c:1947:TRACE_syscall.skip_after_ptrace:Expected 1 (1) == (*__errno_location ()) (0)
TRACE_syscall.skip_after_ptrace: Test failed at step #15
[ FAIL ] TRACE_syscall.skip_after_ptrace
[ RUN ] TRACE_syscall.kill_after_ptrace
TRACE_syscall.kill_after...

With Cosmic s390x KVM, 6 failures reported in our source tree and in the upstream source tree:
[ RUN      ] TRACE_syscall.ptrace_syscall_dropped
TRACE_syscall.ptrace_syscall_dropped: Test failed at step #127
[     FAIL ] TRACE_syscall.ptrace_syscall_dropped
[ RUN      ] TRACE_syscall.syscall_dropped
TRACE_syscall.syscall_dropped: Test failed at step #2
[     FAIL ] TRACE_syscall.syscall_dropped
[ RUN      ] TRACE_syscall.skip_after_RET_TRACE
seccomp_bpf.c:1884:TRACE_syscall.skip_after_RET_TRACE:Expected -1 (18446744073709551615) == syscall(20) (728)
seccomp_bpf.c:1885:TRACE_syscall.skip_after_RET_TRACE:Expected 1 (1) == (*__errno_location ()) (0)
TRACE_syscall.skip_after_RET_TRACE: Test failed at step #12
[     FAIL ] TRACE_syscall.skip_after_RET_TRACE
[ RUN      ] TRACE_syscall.kill_after_RET_TRACE
TRACE_syscall.kill_after_RET_TRACE: Test exited normally instead of by signal (code: 0)
[     FAIL ] TRACE_syscall.kill_after_RET_TRACE
[ RUN      ] TRACE_syscall.skip_after_ptrace
seccomp_bpf.c:1946:TRACE_syscall.skip_after_ptrace:Expected -1 (18446744073709551615) == syscall(20) (728)
seccomp_bpf.c:1947:TRACE_syscall.skip_after_ptrace:Expected 1 (1) == (*__errno_location ()) (0)
TRACE_syscall.skip_after_ptrace: Test failed at step #15
[     FAIL ] TRACE_syscall.skip_after_ptrace
[ RUN      ] TRACE_syscall.kill_after_ptrace
TRACE_syscall.kill_after_ptrace: Test exited normally instead of by signal (code: 0)
[     FAIL ] TRACE_syscall.kill_after_ptrace

With Xenail s390x KVM, the test suite is outdated and it will pass with 54 tests there. With the upstream source tree, there will be 8 failures:
[ RUN      ] global.KILL_process
seccomp_bpf.c:727:global.KILL_process:Expected 0 (0) != (((signed char) ((((__extension__ (((union { __typeof(status) __in; int __i; }) { .__in = (status) }).__i))) & 0x7f) + 1) >> 1) > 0) (0)
global.KILL_process: Test terminated by assertion
[     FAIL ] global.KILL_process
[ RUN      ] TRACE_syscall.ptrace_syscall_dropped
TRACE_syscall.ptrace_syscall_dropped: Test failed at step #223
[     FAIL ] TRACE_syscall.ptrace_syscall_dropped
[ RUN      ] TRACE_syscall.syscall_dropped
TRACE_syscall.syscall_dropped: Test failed at step #2
[     FAIL ] TRACE_syscall.syscall_dropped
[ RUN      ] TRACE_syscall.skip_after_RET_TRACE
seccomp_bpf.c:1884:TRACE_syscall.skip_after_RET_TRACE:Expected -1 (18446744073709551615) == syscall(20) (5486)
seccomp_bpf.c:1885:TRACE_syscall.skip_after_RET_TRACE:Expected 1 (1) == (*__errno_location ()) (0)
TRACE_syscall.skip_after_RET_TRACE: Test failed at step #12
[     FAIL ] TRACE_syscall.skip_after_RET_TRACE
[ RUN      ] TRACE_syscall.kill_after_RET_TRACE
TRACE_syscall.kill_after_RET_TRACE: Test exited normally instead of by signal (code: 0)
[     FAIL ] TRACE_syscall.kill_after_RET_TRACE
[ RUN      ] TRACE_syscall.skip_after_ptrace
seccomp_bpf.c:1946:TRACE_syscall.skip_after_ptrace:Expected -1 (18446744073709551615) == syscall(20) (5486)
seccomp_bpf.c:1947:TRACE_syscall.skip_after_ptrace:Expected 1 (1) == (*__errno_location ()) (0)
TRACE_syscall.skip_after_ptrace: Test failed at step #15
[     FAIL ] TRACE_syscall.skip_after_ptrace
[ RUN      ] TRACE_syscall.kill_after_ptrace
TRACE_syscall.kill_after_ptrace: Test exited normally instead of by signal (code: 0)
[     FAIL ] TRACE_syscall.kill_after_ptrace
[ RUN      ] global.get_metadata
seccomp_bpf.c:2923:global.get_metadata:Expected sizeof(md) (16) == ret (18446744073709551615)
seccomp_bpf.c:2933:global.get_metadata:Expected sizeof(md) (16) == ret (18446744073709551615)
seccomp_bpf.c:2934:global.get_metadata:Expected md.flags (2) == 0 (0)
global.get_metadata: Test failed at step #6
[     FAIL ] global.get_metadata

summary:	- seccomp in ubuntu_kernel_selftest failed on B s390x KVM + seccomp in ubuntu_kernel_selftest failed on X/B/C s390x KVM
tags:	added: cosmic xenial

Revision history for this message

Po-Hsu Lin (cypressyew) wrote on 2018-12-25:

This seccomp test passed on Cosmic AMD64.

Kleber Sacilotto de Souza (kleber-souza) on 2019-07-19

Changed in linux (Ubuntu Cosmic):
status:	New → Won't Fix

Brad Figg (brad-figg) on 2019-07-24

tags:

added: cscc

Po-Hsu Lin (cypressyew) on 2019-09-16

tags:

added: ubuntu-kernel-selftests

Sean Feole (sfeole) on 2019-12-16

Changed in ubuntu-kernel-tests:
status:	New → Triaged
tags:	added: sru-20191202

Revision history for this message

Po-Hsu Lin (cypressyew) wrote on 2023-09-06:

On X-hwe-4.15.0-216.227~16.04.1 openstack s390x instance, this is failing with the following 4 test cases:

[ RUN ] TRACE_syscall.skip_after_RET_TRACE
[ FAIL ] TRACE_syscall.skip_after_RET_TRACE
[ RUN ] TRACE_syscall.kill_after_RET_TRACE
[ FAIL ] TRACE_syscall.kill_after_RET_TRACE
[ RUN ] TRACE_syscall.skip_after_ptrace
[ FAIL ] TRACE_syscall.skip_after_ptrace
[ RUN ] TRACE_syscall.kill_after_ptrace
[ FAIL ] TRACE_syscall.kill_after_ptrace

[==========] 61 / 65 tests passed.

tags:

added: 4.15

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.

ubuntu-kernel-tests

seccomp in ubuntu_kernel_selftest failed on X/B/C s390x KVM

Bug Description

Other bug subscribers

Bug attachments

Remote bug watches