selinux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nicolas Iooss <nicolas.iooss@m4x.org>
To: Petr Lautrbach <plautrba@redhat.com>,
	SElinux list <selinux@vger.kernel.org>
Subject: Re: ANN: SELinux userspace 3.0-rc1 release candidate
Date: Fri, 1 Nov 2019 11:54:57 +0100	[thread overview]
Message-ID: <CAJfZ7=nOVSMNZHCYexgEk=xAfMfEA1pVkvVs5YANurj86VNMug@mail.gmail.com> (raw)
In-Reply-To: <pjd1rut9rnh.fsf@redhat.com>

On Thu, Oct 31, 2019 at 10:43 AM Petr Lautrbach <plautrba@redhat.com> wrote:
>
> Hello,
>
> A 3.0-rc1 release candidate for the SELinux userspace is now
> available at:
>
> https://github.com/SELinuxProject/selinux/wiki/Releases
>
> Please give it a test and let us know if there are any issues.
>
> If there are specific changes that you think should be called out
> in release notes for packagers and users in the final release
> announcement, let us know.

Hello, I started testing this RC on a test virtual machine (which uses
Arch Linux and refpolicy) and something changed in a quite unexpected
way: "semodule --verbose" is now a lot more noisy than 2.9. Here is an
example of what I get when rebuilding the policy:

# semodule --verbose -B
Committing changes:
Disabling optional 'ada_optional_6' at
/var/lib/selinux/refpolicy/tmp/modules/400/ada/cil:63
Failed to resolve typeattributeset statement at
/var/lib/selinux/refpolicy/tmp/modules/400/ada/cil:66
Disabling optional 'anaconda_optional_9' at
/var/lib/selinux/refpolicy/tmp/modules/400/anaconda/cil:183
Failed to resolve typeattributeset statement at
/var/lib/selinux/refpolicy/tmp/modules/400/anaconda/cil:189
Disabling optional 'apache_optional_92' at
/var/lib/selinux/refpolicy/tmp/modules/400/apache/cil:3449
Failed to resolve typeattributeset statement at
/var/lib/selinux/refpolicy/tmp/modules/400/apache/cil:3499
...

Such an output could be useful when debugging issues about optional
modules, but they may make other issues harder to find among all the
messages. Would it be possible to hide these specific messages by
default in verbose mode?

Thanks,
Nicolas


  reply	other threads:[~2019-11-01 10:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-31  9:43 ANN: SELinux userspace 3.0-rc1 release candidate Petr Lautrbach
2019-11-01 10:54 ` Nicolas Iooss [this message]
2019-11-01 13:43   ` [Non-DoD Source] " jwcart2

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='CAJfZ7=nOVSMNZHCYexgEk=xAfMfEA1pVkvVs5YANurj86VNMug@mail.gmail.com' \
    --to=nicolas.iooss@m4x.org \
    --cc=plautrba@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).