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 stress-ng can read+write+map /secretmem anon inodes
Date: Fri, 11 Sep 2026 13:23:25 GMT [thread overview]
Message-ID: <178913300515.1.5287422967258189379.tests-selinux-752ee72f5ab8@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : tests/selinux
Branch : pr775-checkpolicy-revdeps
Commit : 752ee72f5ab8a72cac9d3f2536806294eb187b96
Author : Milos Malik <mmalik@redhat.com>
Date : 2025-11-13T08:16:15+00:00
Stats : +8/-0 in 3 file(s)
URL : https://src.fedoraproject.org/tests/selinux/c/752ee72f5ab8a72cac9d3f2536806294eb187b96?branch=pr775-checkpolicy-revdeps
Log:
test if stress-ng can read+write+map /secretmem anon inodes
Recently, a regular kernel + stress-ng testing revealed that SELinux
prevents the stress-ng program from writing (syscall = ftruncate)
and reading (syscall = mmap) the /secretmem anon inodes. The TC
reproduces the situation.
In order to enable various stress-ng functions, I believe that SELinux
policy should allow the actions mentioned above. The TC looks for
appropriate policy rules and file context patterns.
The TC covers RHEL-116154 and RHELTEST-2022.
---
diff --git a/selinux-policy/anon_inode-and-similar/Makefile b/selinux-policy/anon_inode-and-similar/Makefile
index 69a0f7f..80b8415 100644
--- a/selinux-policy/anon_inode-and-similar/Makefile
+++ b/selinux-policy/anon_inode-and-similar/Makefile
@@ -71,6 +71,8 @@ $(METADATA): Makefile
@echo "Bug: RHEL-11792" >> $(METADATA) # RHEL-9
@echo "Bug: 2270895" >> $(METADATA) # Fedora 41
@echo "Bug: RHEL-60837" >> $(METADATA) # RHEL-10
+ @echo "Bug: RHEL-116154" >> $(METADATA) # RHEL-10
+ @echo "Bug: RHELTEST-2022" >> $(METADATA) # RHEL-10
rhts-lint $(METADATA)
diff --git a/selinux-policy/anon_inode-and-similar/main.fmf b/selinux-policy/anon_inode-and-similar/main.fmf
index 08c5b28..7434a87 100644
--- a/selinux-policy/anon_inode-and-similar/main.fmf
+++ b/selinux-policy/anon_inode-and-similar/main.fmf
@@ -42,6 +42,8 @@ link:
- verifies: https://issues.redhat.com/browse/RHEL-11792
- verifies: https://bugzilla.redhat.com/show_bug.cgi?id=2270895
- verifies: https://issues.redhat.com/browse/RHEL-60837
+ - verifies: https://issues.redhat.com/browse/RHEL-116154
+ - verifies: https://issues.redhat.com/browse/RHELTEST-2022
adjust+:
- enabled: false
when: distro == rhel-4, rhel-5, rhel-6, rhel-7, rhel-8, centos-stream-8
diff --git a/selinux-policy/anon_inode-and-similar/runtest.sh b/selinux-policy/anon_inode-and-similar/runtest.sh
index 8a506d3..0732ea1 100755
--- a/selinux-policy/anon_inode-and-similar/runtest.sh
+++ b/selinux-policy/anon_inode-and-similar/runtest.sh
@@ -107,6 +107,10 @@ rlJournalStart
rlSESearchRule "type_transition sysadm_t sysadm_t : anon_inode secretmem_t [secretmem]"
rlRun "stress-ng --resources 16 --timeout 5 --log-file /dev/null"
rlPhaseEnd
+
+ rlPhaseStartTest "RHEL-116154 + RHELTEST-2022"
+ rlSESearchRule "allow unconfined_t secretmem_t : anon_inode { map read write } [ ]"
+ rlPhaseEnd
fi
rlPhaseStartCleanup
reply other threads:[~2026-09-11 13:23 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=178913300515.1.5287422967258189379.tests-selinux-752ee72f5ab8@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