All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Moore <paul@paul-moore.com>
To: Ondrej Mosnacek <omosnace@redhat.com>
Cc: selinux@vger.kernel.org, Stephen Smalley <sds@tycho.nsa.gov>
Subject: Re: [PATCH] selinux: move status variables out of selinux_ss
Date: Thu, 30 Jan 2020 22:38:42 -0500	[thread overview]
Message-ID: <CAHC9VhTZm08YCg3TOjpN20WeRQ9Fmbg=KMfvKnmD18KjGArv4Q@mail.gmail.com> (raw)
In-Reply-To: <20200117131514.496122-1-omosnace@redhat.com>

On Fri, Jan 17, 2020 at 8:15 AM Ondrej Mosnacek <omosnace@redhat.com> wrote:
>
> It fits more naturally in selinux_state, since it reflects also global
> state (the enforcing and policyload fields).
>
> Signed-off-by: Ondrej Mosnacek <omosnace@redhat.com>
> ---
>  security/selinux/Makefile           |  4 ++--
>  security/selinux/hooks.c            |  1 +
>  security/selinux/include/security.h |  4 ++++
>  security/selinux/ss/services.c      |  2 --
>  security/selinux/ss/services.h      |  2 --
>  security/selinux/{ss => }/status.c  | 32 ++++++++++++++---------------
>  6 files changed, 23 insertions(+), 22 deletions(-)
>  rename security/selinux/{ss => }/status.c (81%)

Makes sense to me too.  I've queued this up in selinux/next, you'll
see it in the tree once the merge window closes.

-- 
paul moore
www.paul-moore.com

      parent reply	other threads:[~2020-01-31  3:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-17 13:15 [PATCH] selinux: move status variables out of selinux_ss Ondrej Mosnacek
2020-01-17 19:48 ` Stephen Smalley
2020-01-31  3:38 ` Paul Moore [this message]

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='CAHC9VhTZm08YCg3TOjpN20WeRQ9Fmbg=KMfvKnmD18KjGArv4Q@mail.gmail.com' \
    --to=paul@paul-moore.com \
    --cc=omosnace@redhat.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 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.