From: Ondrej Mosnacek <omosnace@redhat.com>
To: selinux@vger.kernel.org, Paul Moore <paul@paul-moore.com>
Cc: Stephen Smalley <sds@tycho.nsa.gov>
Subject: [PATCH 0/2] Optimize storage of filename transitions
Date: Tue, 11 Feb 2020 17:39:51 +0100 [thread overview]
Message-ID: <20200211163953.12231-1-omosnace@redhat.com> (raw)
This series improves the computational and memory efficiency of filename
transition rules in SELinux. The first patch is only cosmetic, see the
second patch for more details about its effects.
Ondrej Mosnacek (2):
selinux: factor out loop body from filename_trans_read()
selinux: optimize storage of filename transitions
security/selinux/ss/policydb.c | 227 +++++++++++++++++++--------------
security/selinux/ss/policydb.h | 8 +-
security/selinux/ss/services.c | 16 ++-
3 files changed, 148 insertions(+), 103 deletions(-)
--
2.24.1
next reply other threads:[~2020-02-11 16:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-11 16:39 Ondrej Mosnacek [this message]
2020-02-11 16:39 ` [PATCH 1/2] selinux: factor out loop body from filename_trans_read() Ondrej Mosnacek
2020-02-11 16:39 ` [PATCH 2/2] selinux: optimize storage of filename transitions Ondrej Mosnacek
2020-02-11 20:52 ` Stephen Smalley
2020-02-11 21:32 ` 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=20200211163953.12231-1-omosnace@redhat.com \
--to=omosnace@redhat.com \
--cc=paul@paul-moore.com \
--cc=sds@tycho.nsa.gov \
--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).