| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <c17b2e6c-3626-4d69-8784-01b13a9e2851@linux.dev>
Date: Mon, 9 Jun 2025 14:30:19 -0700
From: Ihor Solodrai <ihor.solodrai@...ux.dev>
To: bpf <bpf@...r.kernel.org>, linux-kernel@...r.kernel.org
Cc: Kernel Team <kernel-team@...a.com>, kernel-ci@...a.com,
Alexei Starovoitov <ast@...nel.org>, tj@...nel.org, mkutsevol@...a.com,
scottbpc@...a.com, jakehillion@...a.com, mykolal@...a.com
Subject: BPF CI update: veristat-scx job
Hi everyone.
In effort to improve testing of both BPF subsystem and sched-ext
project [1], a new testing workflow has been added to BPF CI:
veristat-scx.
veristat-kernel and veristat-meta jobs have been running for a while
now, and veristat-scx is basically adding more test cases using
sched-ext BPF programs as input.
For those who aren't aware, veristat [2] is a command line tool that
can be used to load BPF object files into the kernel and check
verification results, among other things. It's source code is at
./tools/testing/selftests/bpf/veristat.c
On BPF CI, veristat-${target} job takes BPF object files (determined
by ${target}) as input, and runs veristat on them against the kernel
under testing. In addition to checking whether BPF program is accepted
by the verifier, the CI job also collects verifier performance stats,
and compares them to the baseline *failing* if a significant
regression is detected.
See an example of successful job run here:
https://github.com/kernel-patches/bpf/actions/runs/15543439297/job/43761685117
[1] https://github.com/sched-ext/scx
[2] https://github.com/libbpf/veristat
Powered by blists - more mailing lists