All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ondrej Mosnacek <omosnace@redhat.com>
To: selinux@vger.kernel.org
Subject: [PATCH userspace 0/2] Refine semantics of libsemanage's check_ext_changes
Date: Wed,  8 Jun 2022 19:09:52 +0200	[thread overview]
Message-ID: <20220608170954.114668-1-omosnace@redhat.com> (raw)

Make it always do the "do_write_kernel" step so that the semantic is
essentially "--build but with the module content checksum optimization",
as otherwise the final policy doesn't get updated when there are no
changes in modules, but other customizations are applied.

Since the name --rebuild-if-modules-changed no longer matches the
semantics, also change that to just --refresh, which fits better.

Also update man pages and code comments.

Ondrej Mosnacek (2):
  libsemanage: always write kernel policy when check_ext_changes is
    specified
  semodule: rename --rebuild-if-modules-changed to --refresh

 libsemanage/include/semanage/handle.h |  2 +-
 libsemanage/src/direct_api.c          |  8 +++++---
 policycoreutils/semodule/semodule.8   | 12 ++++++------
 policycoreutils/semodule/semodule.c   | 13 ++++++++++---
 4 files changed, 22 insertions(+), 13 deletions(-)

-- 
2.36.1


             reply	other threads:[~2022-06-08 17:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-08 17:09 Ondrej Mosnacek [this message]
2022-06-08 17:09 ` [PATCH userspace 1/2] libsemanage: always write kernel policy when check_ext_changes is specified Ondrej Mosnacek
2022-06-28 21:01   ` Nicolas Iooss
2022-06-29 16:55     ` James Carter
2022-06-30 19:34       ` Nicolas Iooss
2022-06-08 17:09 ` [PATCH userspace 2/2] semodule: rename --rebuild-if-modules-changed to --refresh 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=20220608170954.114668-1-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.