From: Paul Moore <paul@paul-moore.com>
To: omosnace@redhat.com
Cc: selinux@vger.kernel.org, Stephen Smalley <sds@tycho.nsa.gov>,
selinux@tycho.nsa.gov
Subject: Re: [RFC PATCH 1/3] selinux: refactor sidtab conversion
Date: Tue, 20 Nov 2018 16:47:35 -0500 [thread overview]
Message-ID: <CAHC9VhQoJk0KF2B+SEsVO4Av1qT8dTaOPDPkFV=R1J6W49qSYw@mail.gmail.com> (raw)
In-Reply-To: <20181113135255.26045-2-omosnace@redhat.com>
On Tue, Nov 13, 2018 at 8:53 AM Ondrej Mosnacek <omosnace@redhat.com> wrote:
> This is a purely cosmetic change that encapsulates the three-step sidtab
> conversion logic (shutdown -> clone -> map) into a single function
> defined in sidtab.c (as opposed to services.c).
>
> Signed-off-by: Ondrej Mosnacek <omosnace@redhat.com>
> ---
> security/selinux/ss/services.c | 22 +--------------
> security/selinux/ss/sidtab.c | 50 ++++++++++++++++++++++++----------
> security/selinux/ss/sidtab.h | 11 ++++----
> 3 files changed, 42 insertions(+), 41 deletions(-)
Merged into selinux/next with some whitespace fixes (inherited from
code you cut n' pasted). Please remember to run your patches through
scripts/checkpatch.pl before submission.
--
paul moore
www.paul-moore.com
next prev parent reply other threads:[~2018-11-20 21:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-13 13:52 [RFC PATCH 0/3] Fix ENOMEM errors during policy reload Ondrej Mosnacek
2018-11-13 13:52 ` [RFC PATCH 1/3] selinux: refactor sidtab conversion Ondrej Mosnacek
2018-11-13 21:19 ` Stephen Smalley
2018-11-20 21:47 ` Paul Moore [this message]
2018-11-21 8:08 ` Ondrej Mosnacek
2018-11-13 13:52 ` [RFC PATCH 2/3] selinux: use separate table for initial SID lookup Ondrej Mosnacek
2018-11-13 21:37 ` Stephen Smalley
2018-11-14 9:45 ` Ondrej Mosnacek
2018-11-14 14:10 ` Stephen Smalley
2018-11-15 12:52 ` Ondrej Mosnacek
2018-11-13 13:52 ` [RFC PATCH 3/3] selinux: overhaul sidtab to fix bug and improve performance 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='CAHC9VhQoJk0KF2B+SEsVO4Av1qT8dTaOPDPkFV=R1J6W49qSYw@mail.gmail.com' \
--to=paul@paul-moore.com \
--cc=omosnace@redhat.com \
--cc=sds@tycho.nsa.gov \
--cc=selinux@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 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.