All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sebastien Buisson <sbuisson.ddn@gmail.com>
To: Paul Moore <pmoore@redhat.com>, sds@tycho.nsa.gov
Cc: linux-security-module@vger.kernel.org,
	linux-kernel@vger.kernel.org, selinux@tycho.nsa.gov,
	william.c.roberts@intel.com, serge@hallyn.com,
	james.l.morris@oracle.com, Eric Paris <eparis@parisplace.org>,
	Paul Moore <paul@paul-moore.com>,
	Sebastien Buisson <sbuisson@ddn.com>
Subject: Re: [PATCH] selinux: add selinux_is_enforced() function
Date: Wed, 12 Apr 2017 15:30:58 +0200	[thread overview]
Message-ID: <CAPkE-bX5-Mo9AMPwf6dwBNT9FeWgAShWwKbkiJg3ZZVpt9itLA@mail.gmail.com> (raw)
In-Reply-To: <CAGH-KgsymFfRqDnmn1kLpWiPtHFkLU3UMKVu=8=NOUwk+qWjmg@mail.gmail.com>

2017-04-12 13:55 GMT+02:00 Paul Moore <pmoore@redhat.com>:
> As currently written this code isn't something we would want to merge
> upstream for two important reasons:
>
> * No clear user of this functionality.  There needs to be a well
> defined user of this functionality in the kernel.

The use case for this new functionality (and the other one) is getting
SELinux information from the Lustre client code in kernel space.
Latest patch can be accessed at:
https://review.whamcloud.com/24421
Actual user is sptlrpc_get_sepol() function in lustre/lustre/ptlrpc/sec.c file.
This code will be pushed to the upstream kernel as soon as it is
landed into Lustre master branch.

WARNING: multiple messages have this Message-ID (diff)
From: sbuisson.ddn@gmail.com (Sebastien Buisson)
To: linux-security-module@vger.kernel.org
Subject: [PATCH] selinux: add selinux_is_enforced() function
Date: Wed, 12 Apr 2017 15:30:58 +0200	[thread overview]
Message-ID: <CAPkE-bX5-Mo9AMPwf6dwBNT9FeWgAShWwKbkiJg3ZZVpt9itLA@mail.gmail.com> (raw)
In-Reply-To: <CAGH-KgsymFfRqDnmn1kLpWiPtHFkLU3UMKVu=8=NOUwk+qWjmg@mail.gmail.com>

2017-04-12 13:55 GMT+02:00 Paul Moore <pmoore@redhat.com>:
> As currently written this code isn't something we would want to merge
> upstream for two important reasons:
>
> * No clear user of this functionality.  There needs to be a well
> defined user of this functionality in the kernel.

The use case for this new functionality (and the other one) is getting
SELinux information from the Lustre client code in kernel space.
Latest patch can be accessed at:
https://review.whamcloud.com/24421
Actual user is sptlrpc_get_sepol() function in lustre/lustre/ptlrpc/sec.c file.
This code will be pushed to the upstream kernel as soon as it is
landed into Lustre master branch.
--
To unsubscribe from this list: send the line "unsubscribe linux-security-module" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2017-04-12 13:31 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-12  9:06 [PATCH] selinux: add selinux_is_enforced() function Sebastien Buisson
2017-04-12  9:06 ` Sebastien Buisson
2017-04-12 11:55 ` Paul Moore
2017-04-12 11:55   ` Paul Moore
2017-04-12 13:30   ` Sebastien Buisson
2017-04-12 13:30     ` Sebastien Buisson
2017-04-12 13:58     ` Stephen Smalley
2017-04-12 13:58       ` Stephen Smalley
2017-04-12 15:19       ` Sebastien Buisson
2017-04-12 15:19         ` Sebastien Buisson
2017-04-12 16:33         ` Stephen Smalley
2017-04-12 16:33           ` Stephen Smalley
2017-04-13  0:12           ` Casey Schaufler
2017-04-13  0:12             ` Casey Schaufler
2017-04-12 13:30   ` Sebastien Buisson [this message]
2017-04-12 13:30     ` Sebastien Buisson
2017-04-12 14:35     ` Stephen Smalley
2017-04-12 14:35       ` Stephen Smalley
2017-04-12 15:11       ` Sebastien Buisson
2017-04-12 15:11         ` Sebastien Buisson
2017-04-12 16:24         ` Stephen Smalley
2017-04-12 16:24           ` Stephen Smalley
2017-04-12 17:07           ` Sebastien Buisson
2017-04-12 17:07             ` Sebastien Buisson
2017-04-12 17:24             ` Stephen Smalley
2017-04-12 17:24               ` Stephen Smalley
2017-04-12 12:13 ` Stephen Smalley
2017-04-12 12:13   ` 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=CAPkE-bX5-Mo9AMPwf6dwBNT9FeWgAShWwKbkiJg3ZZVpt9itLA@mail.gmail.com \
    --to=sbuisson.ddn@gmail.com \
    --cc=eparis@parisplace.org \
    --cc=james.l.morris@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=paul@paul-moore.com \
    --cc=pmoore@redhat.com \
    --cc=sbuisson@ddn.com \
    --cc=sds@tycho.nsa.gov \
    --cc=selinux@tycho.nsa.gov \
    --cc=serge@hallyn.com \
    --cc=william.c.roberts@intel.com \
    /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.