selinux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Smalley <stephen.smalley.work@gmail.com>
To: Ondrej Mosnacek <omosnace@redhat.com>, selinux@vger.kernel.org
Cc: James Carter <jwcart2@gmail.com>,
	Chris PeBenito <pebenito@ieee.org>,
	Petr Lautrbach <plautrba@redhat.com>
Subject: Re: [PATCH v6 1/2] libsepol,checkpolicy: optimize storage of filename transitions
Date: Thu, 6 Aug 2020 08:02:56 -0400	[thread overview]
Message-ID: <32928866-c2a9-6167-b897-4c54c2940b3f@gmail.com> (raw)
In-Reply-To: <e57f8b36-6134-bc19-35a7-f03a6f7b7bb2@gmail.com>

On 8/3/20 9:56 AM, Stephen Smalley wrote:

> On 7/31/20 7:10 AM, Ondrej Mosnacek wrote:
>
>> In preparation to support a new policy format with a more optimal
>> representation of filename transition rules, this patch applies an
>> equivalent change from kernel commit c3a276111ea2 ("selinux: optimize
>> storage of filename transitions").
>>
>> See the kernel commit's description [1] for the rationale behind this
>> representation. This change doesn't bring any measurable difference of
>> policy build performance (semodule -B) on Fedora.
>>
>> [1] 
>> https://git.kernel.org/pub/scm/linux/kernel/git/pcmoore/selinux.git/commit/?id=c3a276111ea2572399281988b3129683e2a6b60b
>>
>> Signed-off-by: Ondrej Mosnacek <omosnace@redhat.com>
> Acked-by: Stephen Smalley <stephen.smalley.work@gmail.com>
Thanks, applied.

  reply	other threads:[~2020-08-06 17:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-31 11:10 [PATCH v6 0/2] userspace: Implement new format of filename trans rules Ondrej Mosnacek
2020-07-31 11:10 ` [PATCH v6 1/2] libsepol,checkpolicy: optimize storage of filename transitions Ondrej Mosnacek
2020-08-03 13:56   ` Stephen Smalley
2020-08-06 12:02     ` Stephen Smalley [this message]
2020-07-31 11:10 ` [PATCH v6 2/2] libsepol: implement POLICYDB_VERSION_COMP_FTRANS Ondrej Mosnacek
2020-08-03 13:57   ` Stephen Smalley
2020-08-06 12:03     ` 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=32928866-c2a9-6167-b897-4c54c2940b3f@gmail.com \
    --to=stephen.smalley.work@gmail.com \
    --cc=jwcart2@gmail.com \
    --cc=omosnace@redhat.com \
    --cc=pebenito@ieee.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).