From: James Morris <jmorris@namei.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-security-module@vger.kernel.org
Subject: [GIT PULL] security: general updates for 4.20
Date: Tue, 23 Oct 2018 20:22:36 +1100 (AEDT) [thread overview]
Message-ID: <alpine.LRH.2.21.1810232013020.19032@namei.org> (raw)
Hi Linus,
Please pull these general updates for the security subsystem.
In this patchset, there are a couple of minor updates, as well as some
reworking of the LSM initialization code from Kees Cook (these prepare the
way for ordered stackable LSMs, but are a valuable cleanup on their own).
---
The following changes since commit 57361846b52bc686112da6ca5368d11210796804:
Linux 4.19-rc2 (2018-09-02 14:37:30 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/linux-security.git next-general
for you to fetch changes up to 3f6caaf5ff33073ca1a3a0b82edacab3c57c38f9:
LSM: Don't ignore initialization failures (2018-10-10 20:40:22 -0700)
----------------------------------------------------------------
Christian Brauner (1):
security/capabilities: remove check for -EINVAL
David Howells (1):
keys: Fix the use of the C++ keyword "private" in uapi/linux/keyctl.h
Ding Xiang (1):
security: tomoyo: Fix obsolete function
Igor Stoppa (1):
seccomp: remove unnecessary unlikely()
James Morris (1):
Merge tag 'v4.19-rc2' into next-general
Kees Cook (10):
LSM: Correctly announce start of LSM initialization
vmlinux.lds.h: Avoid copy/paste of security_init section
LSM: Rename .security_initcall section to .lsm_info
LSM: Remove initcall tracing
LSM: Convert from initcall to struct lsm_info
vmlinux.lds.h: Move LSM_TABLE into INIT_DATA
LSM: Convert security_initcall() into DEFINE_LSM()
LSM: Record LSM name in struct lsm_info
LSM: Provide init debugging infrastructure
LSM: Don't ignore initialization failures
Randy Dunlap (1):
security: fix LSM description location
Documentation/admin-guide/kernel-parameters.txt | 2 ++
Documentation/security/LSM.rst | 2 +-
arch/arc/kernel/vmlinux.lds.S | 1 -
arch/arm/kernel/vmlinux-xip.lds.S | 1 -
arch/arm64/kernel/vmlinux.lds.S | 1 -
arch/h8300/kernel/vmlinux.lds.S | 1 -
arch/microblaze/kernel/vmlinux.lds.S | 2 --
arch/powerpc/kernel/vmlinux.lds.S | 2 --
arch/um/include/asm/common.lds.S | 2 --
arch/xtensa/kernel/vmlinux.lds.S | 1 -
include/asm-generic/vmlinux.lds.h | 25 +++++++-------
include/linux/init.h | 2 --
include/linux/lsm_hooks.h | 12 +++++++
include/linux/module.h | 1 -
include/uapi/linux/keyctl.h | 7 +++-
kernel/seccomp.c | 4 +--
security/apparmor/lsm.c | 5 ++-
security/commoncap.c | 3 --
security/integrity/iint.c | 6 +++-
security/security.c | 43 ++++++++++++++++---------
security/selinux/hooks.c | 5 ++-
security/smack/smack_lsm.c | 5 ++-
security/tomoyo/common.c | 3 +-
security/tomoyo/tomoyo.c | 5 ++-
24 files changed, 84 insertions(+), 57 deletions(-)
next reply other threads:[~2018-10-23 9:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-23 9:22 James Morris [this message]
2018-10-24 10:51 ` [GIT PULL] security: general updates for 4.20 Linus Torvalds
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=alpine.LRH.2.21.1810232013020.19032@namei.org \
--to=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=torvalds@linux-foundation.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).