kernel/selftests: seccomp_benchmark fails with timeout in H/KVM

Bug #1929247 reported by Guilherme G. Piccoli
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubuntu-kernel-tests
Confirmed
Low
Unassigned
linux-kvm (Ubuntu)
Confirmed
Undecided
Unassigned
Hirsute
New
Undecided
Unassigned

Bug Description

Found that on cycle sru-20210510, on H/KVM 5.11.0-1008.8 :

02:36:23 DEBUG| [stdout] # selftests: seccomp: seccomp_benchmark
02:36:23 DEBUG| [stdout] # sysctl: cannot stat /proc/sys/net/core/bpf_jit_enable: No such file or directory
02:36:23 DEBUG| [stdout] # sysctl: cannot stat /proc/sys/net/core/bpf_jit_harden: No such file or directory
02:38:23 DEBUG| [stdout] #
02:38:23 DEBUG| [stdout] not ok 2 selftests: seccomp: seccomp_benchmark # TIMEOUT 120 seconds

In the previous cycle this test worked, but this one failed due to timeout - I've manually executed in my Hirsute VM and it succeeded in ~100 seconds.

Maybe we need to just bump the timeout.

Changed in linux-kvm (Ubuntu):
assignee: nobody → Guilherme G. Piccoli (gpiccoli)
assignee: Guilherme G. Piccoli (gpiccoli) → nobody
Changed in ubuntu-kernel-tests:
assignee: Guilherme G. Piccoli (gpiccoli) → nobody
Changed in linux-kvm (Ubuntu):
status: New → Confirmed
tags: added: sru-20210927
Revision history for this message
Tim Gardner (timg-tpi) wrote :

Seen with aws 5.11.0-1021.22 on m5a.large and r5.metal

tags: added: aws sru-20211018
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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