SELinux Security Module development
 help / color / mirror / Atom feed
From: Petr Lautrbach <plautrba@redhat.com>
To: "Christian Göttsche" <cgzones@googlemail.com>, selinux@vger.kernel.org
Subject: Re: [PATCH v2 3/6] libsepol/cil: post process pirqcon rules
Date: Wed, 06 Apr 2022 16:35:15 +0200	[thread overview]
Message-ID: <87v8vmnuu4.fsf@redhat.com> (raw)
In-Reply-To: <20220405133548.51598-3-cgzones@googlemail.com>

Christian Göttsche <cgzones@googlemail.com> writes:

> Signed-off-by: Christian Göttsche <cgzones@googlemail.com>

Already merged from
https://patchwork.kernel.org/project/selinux/patch/20220331144752.31495-3-cgzones@googlemail.com/
based on ack from
https://lore.kernel.org/all/CAP+JOzTokM6k+wTVneEeSLGGhH5A2r7XayLLotiu8XuFn=GW7g@mail.gmail.com/


> ---
>  libsepol/cil/src/cil_post.c | 6 ++++++
>  1 file changed, 6 insertions(+)
>
> diff --git a/libsepol/cil/src/cil_post.c b/libsepol/cil/src/cil_post.c
> index 7f33cd9e..714ce227 100644
> --- a/libsepol/cil/src/cil_post.c
> +++ b/libsepol/cil/src/cil_post.c
> @@ -2434,6 +2434,12 @@ static int cil_post_db(struct cil_db *db)
>  		goto exit;
>  	}
>  
> +	rc = __cil_post_process_context_rules(db->pirqcon, cil_post_pirqcon_compare, cil_post_pirqcon_context_compare, db, CIL_PIRQCON, CIL_KEY_IOMEMCON);
> +	if (rc != SEPOL_OK) {
> +		cil_log(CIL_ERR, "Problems processing pirqcon rules\n");
> +		goto exit;
> +	}
> +
>  	rc = __cil_post_process_context_rules(db->iomemcon, cil_post_iomemcon_compare, cil_post_iomemcon_context_compare, db, CIL_IOMEMCON, CIL_KEY_IOMEMCON);
>  	if (rc != SEPOL_OK) {
>  		cil_log(CIL_ERR, "Problems processing iomemcon rules\n");
> -- 
> 2.35.1


  reply	other threads:[~2022-04-06 17:12 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-31 14:47 [RFC PATCH 1/4] libsepol/cil: declare file local functions static Christian Göttsche
2022-03-31 14:47 ` [RFC PATCH 2/4] libsepol/cil: drop unused function cil_tree_error Christian Göttsche
2022-04-01 20:51   ` James Carter
2022-03-31 14:47 ` [RFC PATCH 3/4] libsepol/cil: post process pirqcon rules Christian Göttsche
2022-04-01 20:51   ` James Carter
2022-03-31 14:47 ` [RFC PATCH 4/4] Enable missing prototypes Christian Göttsche
2022-04-01 20:58   ` James Carter
2022-04-01 20:50 ` [RFC PATCH 1/4] libsepol/cil: declare file local functions static James Carter
2022-04-05 13:35 ` [PATCH v2 1/6] " Christian Göttsche
2022-04-05 13:35   ` [PATCH v2 2/6] libsepol/cil: drop unused function cil_tree_error Christian Göttsche
2022-04-06 14:33     ` Petr Lautrbach
2022-04-05 13:35   ` [PATCH v2 3/6] libsepol/cil: post process pirqcon rules Christian Göttsche
2022-04-06 14:35     ` Petr Lautrbach [this message]
2022-04-05 13:35   ` [PATCH v2 4/6] libsepol/cil: comment out unused function __cil_verify_rule Christian Göttsche
2022-04-06 16:15     ` James Carter
2022-04-20 19:04       ` James Carter
2022-04-05 13:35   ` [PATCH v2 5/6] libsemanage: ignore missing prototypes in swig generated code Christian Göttsche
2022-04-05 13:35   ` [PATCH v2 6/6] Enable missing prototypes Christian Göttsche
2022-04-12 18:14     ` James Carter
2022-04-06 14:29   ` [PATCH v2 1/6] libsepol/cil: declare file local functions static Petr Lautrbach

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=87v8vmnuu4.fsf@redhat.com \
    --to=plautrba@redhat.com \
    --cc=cgzones@googlemail.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