From: Daniel J Walsh <dwalsh@redhat.com>
To: Joshua Brindle <brindle@quarksecurity.com>,
Stephen Smalley <sds@tycho.nsa.gov>
Cc: SELinux-NSA <SELinux@tycho.nsa.gov>
Subject: Re: [RFC] [PATCH] libsemanage: Skip policy module re-link when only setting booleans.
Date: Fri, 25 Jul 2014 15:49:46 -0400 [thread overview]
Message-ID: <53D2B4DA.7090504@redhat.com> (raw)
In-Reply-To: <53D2B3ED.2070102@quarksecurity.com>
How large is it? Does it matter if it is compressed?
On 07/25/2014 03:45 PM, Joshua Brindle wrote:
> Stephen Smalley wrote:
>> Motivated by:
>> https://bugzilla.redhat.com/show_bug.cgi?id=1098446
>>
>> I believe this is always safe for booleans because we only set their
>> value; we are never adding new ones via semanage, unlike for example
>> users, ports, nodes, and interfaces. For the rest, I was wondering why
>> we don't save the linked file and just reuse it on those changes rather
>> than re-linking each time - that seems like it would be straightforward
>
> We originally kept the linked copy around and had intended to do what
> you are saying above but removed it when the minimal Red Hat guys
> complained about the size of it.
>
>> to do in libsemanage and make those operations significantly faster and
>> less memory intensive.
>
next prev parent reply other threads:[~2014-07-25 19:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-25 17:02 [RFC] [PATCH] libsemanage: Skip policy module re-link when only setting booleans Stephen Smalley
2014-07-25 18:35 ` Daniel J Walsh
2014-07-25 19:45 ` Joshua Brindle
2014-07-25 19:49 ` Daniel J Walsh [this message]
2014-07-25 19:55 ` Stephen Smalley
2014-07-25 20:04 ` Joshua Brindle
2014-07-25 20:12 ` Stephen Smalley
2014-07-29 13:15 ` Steve Lawrence
2014-07-28 18:54 ` Daniel J Walsh
2014-08-05 8:30 ` Russell Coker
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=53D2B4DA.7090504@redhat.com \
--to=dwalsh@redhat.com \
--cc=SELinux@tycho.nsa.gov \
--cc=brindle@quarksecurity.com \
--cc=sds@tycho.nsa.gov \
/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.