selinux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Smalley <stephen.smalley.work@gmail.com>
To: James Carter <jwcart2@gmail.com>
Cc: selinux@vger.kernel.org, russell@coker.com.au,
	 Chris PeBenito <pebenito@ieee.org>,
	selinux-refpolicy@vger.kernel.org
Subject: Re: [PATCH 2/2] checkpolicy/tests: Modify tests to check handling of initial sids
Date: Fri, 7 Nov 2025 11:04:35 -0500	[thread overview]
Message-ID: <CAEjxPJ5qFr8iGs=sjoYfb92dFuxjffcsvArASr3f6syc-PcMeA@mail.gmail.com> (raw)
In-Reply-To: <CAEjxPJ5F7CQL26n_LzhfVeaHu4JX3_NmSzTLJObDP=yvTvZjAg@mail.gmail.com>

On Wed, Nov 5, 2025 at 2:00 PM Stephen Smalley
<stephen.smalley.work@gmail.com> wrote:
>
> On Tue, Nov 4, 2025 at 3:52 PM James Carter <jwcart2@gmail.com> wrote:
> >
> > For policy_allonce.conf and policy_allonce_xen.conf declare the
> > first three initial sids, but only assign a context to the first
> > and third. This will cause the second initial sid to be dropped
> > from the binary policy and cause the handling of a gap in the
> > initial sids to be tested.
> >
> > Update the expected and expected_opt policies to reflect the new
> > expected resulting policies.
> >
> > Signed-off-by: James Carter <jwcart2@gmail.com>
>
> Acked-by: Stephen Smalley <stephen.smalley.work@gmail.com>
> Tested-by: Stephen Smalley <stephen.smalley.work@gmail.com>

Thanks, both patches now applied.

  reply	other threads:[~2025-11-07 16:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-04 20:52 [PATCH 1/2] libsepol: Fix sid handling when writing out policy from binary James Carter
2025-11-04 20:52 ` [PATCH 2/2] checkpolicy/tests: Modify tests to check handling of initial sids James Carter
2025-11-05 19:00   ` Stephen Smalley
2025-11-07 16:04     ` Stephen Smalley [this message]
2025-11-05 18:58 ` [PATCH 1/2] libsepol: Fix sid handling when writing out policy from binary Stephen Smalley

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='CAEjxPJ5qFr8iGs=sjoYfb92dFuxjffcsvArASr3f6syc-PcMeA@mail.gmail.com' \
    --to=stephen.smalley.work@gmail.com \
    --cc=jwcart2@gmail.com \
    --cc=pebenito@ieee.org \
    --cc=russell@coker.com.au \
    --cc=selinux-refpolicy@vger.kernel.org \
    --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).