public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Zdenek Pytela <zpytela@redhat.com>
To: git-commits@fedoraproject.org
Subject: [tests/selinux] pr775-checkpolicy-revdeps: Use "${PREFIX}/run/named" for context check
Date: Fri, 11 Sep 2026 13:21:45 GMT [thread overview]
Message-ID: <178913290549.1.267504601708574475.tests-selinux-bbea4d16a352@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : tests/selinux
Branch : pr775-checkpolicy-revdeps
Commit : bbea4d16a352bf3702b646d82f361fcf95d6a7ad
Author : Zdenek Pytela <zpytela@redhat.com>
Date : 2024-06-24T12:11:18+00:00
Stats : +1/-1 in 1 file(s)
URL : https://src.fedoraproject.org/tests/selinux/c/bbea4d16a352bf3702b646d82f361fcf95d6a7ad?branch=pr775-checkpolicy-revdeps
Log:
Use "${PREFIX}/run/named" for context check
Change context check from "${PREFIX}/var/run/named" to
"${PREFIX}/run/named" which matches the actual filesystem state
created and used by the bind-chroot service.
---
diff --git a/selinux-policy/bz562833-chrooted-named-file-contexts/runtest.sh b/selinux-policy/bz562833-chrooted-named-file-contexts/runtest.sh
index 1c88600..7b6ddd4 100755
--- a/selinux-policy/bz562833-chrooted-named-file-contexts/runtest.sh
+++ b/selinux-policy/bz562833-chrooted-named-file-contexts/runtest.sh
@@ -60,12 +60,12 @@ rlJournalStart
rlSEMatchPathCon "${PREFIX}/dev/random" "random_device_t"
rlSEMatchPathCon "${PREFIX}/dev/zero" "zero_device_t"
rlSEMatchPathCon "${PREFIX}/etc/named.conf" "named_conf_t"
+ rlSEMatchPathCon "${PREFIX}/run/named" "named_var_run_t"
rlSEMatchPathCon "${PREFIX}/var/log" "var_log_t"
rlSEMatchPathCon "${PREFIX}/var/log/named.log" "named_log_t"
rlSEMatchPathCon "${PREFIX}/var/named/data" "named_cache_t"
rlSEMatchPathCon "${PREFIX}/var/named/slaves" "named_cache_t"
rlSEMatchPathCon "${PREFIX}/var/named" "named_zone_t"
- rlSEMatchPathCon "${PREFIX}/var/run/named" "named_var_run_t"
done
rlPhaseEnd
reply other threads:[~2026-09-11 13:21 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=178913290549.1.267504601708574475.tests-selinux-bbea4d16a352@fedoraproject.org \
--to=zpytela@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