public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Milos Malik <mmalik@redhat.com>
To: git-commits@fedoraproject.org
Subject: [tests/selinux] pr775-checkpolicy-revdeps: test if stalld can read /sys/kernel/security/lockdown
Date: Fri, 11 Sep 2026 13:20:16 GMT [thread overview]
Message-ID: <178913281645.1.6633129483130827708.tests-selinux-09f8be4247dc@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : tests/selinux
Branch : pr775-checkpolicy-revdeps
Commit : 09f8be4247dc7711a965c4aea42226a2880a4051
Author : Milos Malik <mmalik@redhat.com>
Date : 2022-11-07T18:28:29+01:00
Stats : +7/-0 in 3 file(s)
URL : https://src.fedoraproject.org/tests/selinux/c/09f8be4247dc7711a965c4aea42226a2880a4051?branch=pr775-checkpolicy-revdeps
Log:
test if stalld can read /sys/kernel/security/lockdown
Recent stalld testing identified the following error messages in the
systemd journal:
stalld[...]: stalld: Permission denied
Deeper investigation revealed that SELinux prevents the stalld
processes from reading the /sys/kernel/security/lockdown file. The
TC reproduces the situation.
In order to avoid the error messages, I believe that SELinux policy
should allow the access. The TC looks for appropriate policy rules
and file context patterns.
The TC covers BZ#2140673.
---
diff --git a/selinux-policy/stalld-and-similar/Makefile b/selinux-policy/stalld-and-similar/Makefile
index 5eacb61..507e472 100644
--- a/selinux-policy/stalld-and-similar/Makefile
+++ b/selinux-policy/stalld-and-similar/Makefile
@@ -68,6 +68,7 @@ $(METADATA): Makefile
@echo "Bug: 2096776" >> $(METADATA) # RHEL-9
@echo "Bug: 2102224" >> $(METADATA) # RHEL-9
@echo "Bug: 2105038" >> $(METADATA) # RHEL-9
+ @echo "Bug: 2140673" >> $(METADATA) # RHEL-9
rhts-lint $(METADATA)
diff --git a/selinux-policy/stalld-and-similar/main.fmf b/selinux-policy/stalld-and-similar/main.fmf
index 8ae96f0..515ad87 100644
--- a/selinux-policy/stalld-and-similar/main.fmf
+++ b/selinux-policy/stalld-and-similar/main.fmf
@@ -37,6 +37,7 @@ link:
- verifies: https://bugzilla.redhat.com/show_bug.cgi?id=2096776
- verifies: https://bugzilla.redhat.com/show_bug.cgi?id=2102224
- verifies: https://bugzilla.redhat.com/show_bug.cgi?id=2105038
+ - verifies: https://bugzilla.redhat.com/show_bug.cgi?id=2140673
adjust:
- enabled: false
when: distro == rhel-4, rhel-5, rhel-6, rhel-7, rhel-8
diff --git a/selinux-policy/stalld-and-similar/runtest.sh b/selinux-policy/stalld-and-similar/runtest.sh
index ea131ad..909a0b5 100755
--- a/selinux-policy/stalld-and-similar/runtest.sh
+++ b/selinux-policy/stalld-and-similar/runtest.sh
@@ -91,6 +91,11 @@ rlJournalStart
rlRun "sesearch -s stalld_t -t domain -c process -p setsched -A -ds -dt | grep allow"
rlPhaseEnd
+ rlPhaseStartTest "bz#2140673"
+ rlRun "ls -Z /sys/kernel/security/lockdown | grep :security_t"
+ rlSESearchRule "allow stalld_t security_t : file { getattr open read } [ ]"
+ rlPhaseEnd
+
rlPhaseStartTest "real scenario -- standalone service"
if ! rlSEDefined ${PROCESS_CONTEXT} ; then
PROCESS_CONTEXT="unconfined_service_t"
reply other threads:[~2026-09-11 13:20 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=178913281645.1.6633129483130827708.tests-selinux-09f8be4247dc@fedoraproject.org \
--to=mmalik@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