linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Casey Schaufler <casey@schaufler-ca.com>
To: James Morris <jmorris@namei.org>,
	James Morris <james.l.morris@oracle.com>,
	LSM <linux-security-module@vger.kernel.org>,
	LKLM <linux-kernel@vger.kernel.org>
Cc: Paul Moore <pmoore@redhat.com>,
	John Johansen <john.johansen@canonical.com>,
	Tetsuo Handa <penguin-kernel@i-love.sakura.ne.jp>,
	Stephen Smalley <sds@tycho.nsa.gov>,
	Eric Paris <eparis@redhat.com>, Kees Cook <keescook@chromium.org>,
	Casey Schaufler <casey@schaufler-ca.com>
Subject: [PULL] LSM: Basic module stacking infrastructure for security-next - Acked
Date: Fri, 08 May 2015 19:07:09 -0700	[thread overview]
Message-ID: <554D6BCD.7090009@schaufler-ca.com> (raw)
In-Reply-To: <55454539.9020204@schaufler-ca.com>

James, here's an updated pull request for LSM stacking.
Acks have been applied.

The following changes since commit b787f68c36d49bb1d9236f403813641efa74a031:

  Linux 4.1-rc1 (2015-04-26 17:59:10 -0700)

are available in the git repository at:

  git@github.com:cschaufler/smack-next.git stacking-v22-acked

for you to fetch changes up to f17cd945a8761544ac9bfdaf55e952e558dbee3e:

  LSM: Remove unused capability.c (2015-05-08 11:37:27 -0700)

Signed-off-by: Casey Schaufler <casey@schaufler-ca.com>
Acked-by: John Johansen <john.johansen@canonical.com>
Acked-by: Kees Cook <keescook@chromium.org>
Acked-by: Paul Moore <paul@paul-moore.com>
Acked-by:  Stephen Smalley <sds@tycho.nsa.gov>
Acked-by: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>

----------------------------------------------------------------
Casey Schaufler (7):
      LSM: Split security.h
      LSM: Add the comment to lsm_hooks.h
      LSM: Remove a comment from security.h
      LSM: Introduce security hook calling Macros
      LSM: Add security module hook list heads
      LSM: Switch to lists of hooks
      LSM: Remove unused capability.c

 include/linux/lsm_hooks.h  | 1886
++++++++++++++++++++++++++++++++++++++++++++
 include/linux/security.h   | 1621 +------------------------------------
 security/Makefile          |    2 +-
 security/apparmor/domain.c |   12 +-
 security/apparmor/lsm.c    |  131 ++-
 security/capability.c      | 1158 ---------------------------
 security/commoncap.c       |   41 +-
 security/security.c        |  955 +++++++++++++++-------
 security/selinux/hooks.c   |  490 +++++-------
 security/smack/smack.h     |    4 +-
 security/smack/smack_lsm.c |  307 ++++---
 security/smack/smackfs.c   |    2 +-
 security/tomoyo/tomoyo.c   |   72 +-
 security/yama/yama_lsm.c   |   60 +-
 14 files changed, 3064 insertions(+), 3677 deletions(-)
 create mode 100644 include/linux/lsm_hooks.h
 delete mode 100644 security/capability.c


  parent reply	other threads:[~2015-05-09  2:07 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-02 21:44 [PATCH 0/7 v22] LSM: Multiple concurrent LSMs Casey Schaufler
2015-05-02 22:10 ` [PATCH 1/7 v22] LSM: Split security.h Casey Schaufler
2015-05-07 20:41   ` Paul Moore
2015-05-02 22:10 ` [PATCH 2/7 v22] LSM: Add the comment to lsm_hooks.h Casey Schaufler
2015-05-07 20:42   ` Paul Moore
2015-05-02 22:11 ` [PATCH 3/7 v22] LSM: Remove a comment from security.h Casey Schaufler
2015-05-07 20:43   ` Paul Moore
2015-05-02 22:11 ` [PATCH 4/7 v22] LSM: Introduce security hook calling Macros Casey Schaufler
2015-05-07 21:02   ` Paul Moore
2015-05-02 22:11 ` [PATCH 5/7 v22] LSM: Add security module hook list heads Casey Schaufler
2015-05-07 21:03   ` Paul Moore
2015-05-02 22:11 ` [PATCH 6/7 v22] LSM: Switch to lists of hooks Casey Schaufler
2015-05-07 21:05   ` Paul Moore
2015-05-02 22:11 ` [PATCH 7/7 v22] LSM: Remove unused capability.c Casey Schaufler
2015-05-07 21:05   ` Paul Moore
2015-05-03 19:04 ` [PULL] LSM: Basic module stacking infrastructure for security-next Casey Schaufler
2015-05-07 11:37 ` [PATCH 0/7 v22] LSM: Multiple concurrent LSMs James Morris
2015-05-07 14:47   ` Casey Schaufler
2015-05-07 18:07     ` Paul Moore
2015-05-07 20:22       ` Mimi Zohar
2015-05-07 20:23         ` Stephen Smalley
2015-05-07 20:36           ` Casey Schaufler
2015-05-08 11:21             ` Mimi Zohar
2015-05-08 16:13               ` Casey Schaufler
2015-05-08 17:00                 ` Kees Cook
2015-05-08 17:54                   ` John Johansen
2015-05-09  1:41                     ` Tetsuo Handa
2015-05-07 17:04 ` Stephen Smalley
2015-05-09  2:07 ` Casey Schaufler [this message]
2015-05-12  5:02   ` [PULL] LSM: Basic module stacking infrastructure for security-next - Acked James Morris
2015-05-13  4:19     ` Casey Schaufler
2015-05-15 12:56       ` [PULL] LSM: Basic module stacking infrastructure for security-next- Acked Tetsuo Handa
2015-05-16 17:39         ` Casey Schaufler
2015-05-17  3:53           ` LSM: Basic module stacking infrastructure for security-next-Acked Tetsuo Handa
2015-05-19 17:45       ` [PULL] LSM: Basic module stacking infrastructure for security-next - Acked Kees Cook

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=554D6BCD.7090009@schaufler-ca.com \
    --to=casey@schaufler-ca.com \
    --cc=eparis@redhat.com \
    --cc=james.l.morris@oracle.com \
    --cc=jmorris@namei.org \
    --cc=john.johansen@canonical.com \
    --cc=keescook@chromium.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=penguin-kernel@i-love.sakura.ne.jp \
    --cc=pmoore@redhat.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 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).