From: Petr Lautrbach <plautrba@redhat.com>
To: James Carter <jwcart2@gmail.com>, selinux@vger.kernel.org
Subject: Re: [PATCH 2/2] secilc/docs: Document the order that inherited rules are resolved in
Date: Mon, 31 May 2021 14:05:07 +0200 [thread overview]
Message-ID: <87k0nfcdn0.fsf@redhat.com> (raw)
In-Reply-To: <20210506170537.146337-2-jwcart2@gmail.com>
James Carter <jwcart2@gmail.com> writes:
> In the blockinherit section of the CIL documentation clearly state
> the order in which inherited rules are resolved.
>
> That order is:
>
> 1) The parent namespaces (if any) where the blockinherit rule is
> located with the exception of the global namespace.
>
> 2) The parent namespaces of the block being inherited (but not that
> block's namespace) with the exception of the global namespace.
>
> 3) The global namespace.
>
> Signed-off-by: James Carter <jwcart2@gmail.com>
Both
Acked-by: Petr Lautrbach <plautrba@redhat.com>
and merged.
Thanks!
> ---
> secilc/docs/cil_container_statements.md | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/secilc/docs/cil_container_statements.md b/secilc/docs/cil_container_statements.md
> index 7a7f67cc..41a4612c 100644
> --- a/secilc/docs/cil_container_statements.md
> +++ b/secilc/docs/cil_container_statements.md
> @@ -103,6 +103,14 @@ blockinherit
>
> Used to add common policy rules to the current namespace via a template that has been defined with the [`blockabstract`](cil_container_statements.md#blockabstract) statement. All [`blockinherit`](cil_container_statements.md#blockinherit) statements are resolved first and then the contents of the block are copied. This is so that inherited blocks will not be inherited. For a concrete example, please see the examples section.
>
> +Inherited rules are resolved by searching namespaces in the following order:
> +
> +- The parent namespaces (if any) where the [`blockinherit`](cil_container_statements.md#blockinherit) rule is located with the exception of the global namespace.
> +
> +- The parent namespaces of the block being inherited (but not that block's namespace) with the exception of the global namespace.
> +
> +- The global namespace.
> +
> Not allowed in [`macro`](cil_call_macro_statements.md#macro) blocks.
>
> **Statement definition:**
> --
> 2.26.3
next prev parent reply other threads:[~2021-05-31 12:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-06 17:05 [PATCH 1/2] libsepol/cil: Fix name resolution involving inherited blocks James Carter
2021-05-06 17:05 ` [PATCH 2/2] secilc/docs: Document the order that inherited rules are resolved in James Carter
2021-05-31 12:05 ` Petr Lautrbach [this message]
2021-05-06 17:37 ` [PATCH 1/2] libsepol/cil: Fix name resolution involving inherited blocks Dominick Grift
2021-05-06 18:46 ` James Carter
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=87k0nfcdn0.fsf@redhat.com \
--to=plautrba@redhat.com \
--cc=jwcart2@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox