public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Ondrej Mosnacek <omosnace@redhat.com>
To: git-commits@fedoraproject.org
Subject: [tests/selinux] pr775-checkpolicy-revdeps: kernel/selinux-testsuite: work around CKI BTF issue
Date: Fri, 11 Sep 2026 13:17:59 GMT [thread overview]
Message-ID: <178913267973.1.15538432981507234387.tests-selinux-292f0937bec9@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : tests/selinux
Branch : pr775-checkpolicy-revdeps
Commit : 292f0937bec9ce945bc622e4d753a6a938447e33
Author : Ondrej Mosnacek <omosnace@redhat.com>
Date : 2020-06-01T19:17:25+02:00
Stats : +9/-0 in 1 file(s)
URL : https://src.fedoraproject.org/tests/selinux/c/292f0937bec9ce945bc622e4d753a6a938447e33?branch=pr775-checkpolicy-revdeps
Log:
kernel/selinux-testsuite: work around CKI BTF issue
The CKI kernels are cross-compiled on x86_64, so they generate an
invalid (little-endian) in-kernel BTF on big-endian systems. Work around
this by skipping the BPF test if little-endian BTF is detected on s390x.
Signed-off-by: Ondrej Mosnacek <omosnace@redhat.com>
---
diff --git a/kernel/selinux-testsuite/runtest.sh b/kernel/selinux-testsuite/runtest.sh
index 27c2969..5f18ed6 100755
--- a/kernel/selinux-testsuite/runtest.sh
+++ b/kernel/selinux-testsuite/runtest.sh
@@ -367,6 +367,15 @@ rlJournalStart
exclude_tests+=" module_load"
fi
+ # CKI kernels are cross-compiled and generate invalid BTF for s390x
+ if [ "$(rlGetPrimaryArch)" = s390x ] && [ -r /sys/kernel/btf/vmlinux ]; then
+ # Check whether the magic number is stored big-endian
+ btf_head="$(head -c 2 /sys/kernel/btf/vmlinux | hexdump -e '/1 "%02x"')"
+ if [ "$btf_head" != eb9f ]; then
+ exclude_tests+=" bpf"
+ fi
+ fi
+
if [ -n "$exclude_tests" ] ; then
rlRun "sed -i '/^[^[:space:]]*:\(\| .*\)\$/i SUBDIRS:=\$(filter-out $exclude_tests, \$(SUBDIRS))' tests/Makefile" 0 \
"Exclude not applicable tests: $exclude_tests"
reply other threads:[~2026-09-11 13:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=178913267973.1.15538432981507234387.tests-selinux-292f0937bec9@fedoraproject.org \
--to=omosnace@redhat.com \
--cc=git-commits@fedoraproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox