All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ondrej Mosnacek <omosnace@redhat.com>
To: selinux@vger.kernel.org
Subject: [PATCH testsuite v2 2/3] policy: add fallbacks for Fedora-specific macros
Date: Fri, 15 Nov 2019 16:16:22 +0100	[thread overview]
Message-ID: <20191115151623.265770-3-omosnace@redhat.com> (raw)
In-Reply-To: <20191115151623.265770-1-omosnace@redhat.com>

dev_rw_infiniband_dev() and mount_rw_pid_files() are not defined in
refpolicy. Fall back to dev_rw_generic_files() and
mount_rw_runtime_files() if they are not defined.

Signed-off-by: Ondrej Mosnacek <omosnace@redhat.com>
---
 policy/test_policy.if | 14 ++++++++++++++
 1 file changed, 14 insertions(+)

diff --git a/policy/test_policy.if b/policy/test_policy.if
index 40e7499..e31345e 100644
--- a/policy/test_policy.if
+++ b/policy/test_policy.if
@@ -71,3 +71,17 @@ interface(`userdom_search_generic_user_home_dirs', `
     userdom_search_user_home_content($1)
 ')
 ')
+
+# Workarounds for refpolicy:
+
+ifdef(`dev_rw_infiniband_dev', `', ` dnl
+interface(`dev_rw_infiniband_dev', `
+    dev_rw_generic_files($1)
+')
+')
+
+ifdef(`mount_rw_pid_files', `', ` dnl
+interface(`mount_rw_pid_files', `
+    mount_rw_runtime_files($1)
+')
+')
-- 
2.23.0


  parent reply	other threads:[~2019-11-15 15:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-15 15:16 [PATCH testsuite v2 0/3] Fix refpolicy build & build test_policy.pp in Travis Ondrej Mosnacek
2019-11-15 15:16 ` [PATCH testsuite v2 1/3] policy: consolidate macros for home dirs access Ondrej Mosnacek
2019-11-15 15:16 ` Ondrej Mosnacek [this message]
2019-11-15 15:16 ` [PATCH testsuite v2 3/3] travis: test building the test policy package Ondrej Mosnacek
2019-11-15 15:28 ` [PATCH testsuite v2 0/3] Fix refpolicy build & build test_policy.pp in Travis Ondrej Mosnacek
2019-11-15 15:52 ` Stephen Smalley
2019-11-15 15:59   ` Ondrej Mosnacek

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=20191115151623.265770-3-omosnace@redhat.com \
    --to=omosnace@redhat.com \
    --cc=selinux@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.