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 v4.21
Date: Tue, 25 Dec 2018 06:55:00 +1100 (AEDT) [thread overview]
Message-ID: <alpine.LRH.2.21.1812250652420.2714@namei.org> (raw)
Hi Linus,
Please pull these general updates for the security subsystem for v4.21.
The main changes here are Paul Gortmaker's removal of unneccesary module.h
infrastructure.
The following changes since commit 7566ec393f4161572ba6f11ad5171fd5d59b0fbd:
Linux 4.20-rc7 (2018-12-16 15:46:55 -0800)
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 b49d564344f773d8afee982153c8493e5f2eaf38:
security: integrity: partial revert of make ima_main explicitly non-modular (2018-12-20 09:59:12 -0800)
----------------------------------------------------------------
James Morris (2):
Merge tag 'v4.20-rc2' into next-general
Merge tag 'v4.20-rc7' into next-general
Paul Gortmaker (6):
security: integrity: make ima_main explicitly non-modular
keys: remove needless modular infrastructure from ecryptfs_format
security: integrity: make evm_main explicitly non-modular
security: audit and remove any unnecessary uses of module.h
security: fs: make inode explicitly non-modular
security: integrity: partial revert of make ima_main explicitly non-modular
Yangtao Li (1):
tomoyo: fix small typo
security/apparmor/apparmorfs.c | 2 +-
security/commoncap.c | 1 -
security/inode.c | 6 ++----
security/integrity/evm/evm_crypto.c | 2 +-
security/integrity/evm/evm_main.c | 5 +----
security/integrity/evm/evm_posix_acl.c | 1 -
security/integrity/evm/evm_secfs.c | 2 +-
security/integrity/iint.c | 2 +-
security/integrity/ima/ima_api.c | 1 -
security/integrity/ima/ima_appraise.c | 2 +-
security/integrity/ima/ima_fs.c | 2 +-
security/integrity/ima/ima_init.c | 2 +-
security/integrity/ima/ima_main.c | 5 ++---
security/integrity/ima/ima_policy.c | 2 +-
security/integrity/ima/ima_queue.c | 1 -
security/keys/encrypted-keys/ecryptfs_format.c | 5 ++---
security/keys/encrypted-keys/masterkey_trusted.c | 1 -
security/keys/gc.c | 1 -
security/keys/key.c | 2 +-
security/keys/keyctl.c | 1 -
security/keys/keyring.c | 2 +-
security/keys/permission.c | 2 +-
security/keys/proc.c | 1 -
security/keys/process_keys.c | 1 -
security/keys/request_key.c | 2 +-
security/keys/request_key_auth.c | 1 -
security/keys/user_defined.c | 2 +-
security/security.c | 2 +-
security/tomoyo/util.c | 2 +-
29 files changed, 22 insertions(+), 39 deletions(-)
next reply other threads:[~2018-12-24 19:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-24 19:55 James Morris [this message]
2018-12-27 20:07 ` [GIT PULL] security: general updates for v4.21 Linus Torvalds
2018-12-29 3:11 ` James Morris
2018-12-29 3:39 ` Linus Torvalds
2018-12-29 4:09 ` James Morris
2018-12-29 4:15 ` Linus Torvalds
2018-12-29 18:34 ` Casey Schaufler
2018-12-30 2:44 ` Mimi Zohar
2019-01-07 21:45 ` James Morris
2019-01-08 21:56 ` Mimi Zohar
2018-12-27 22:05 ` pr-tracker-bot
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.1812250652420.2714@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).