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 subsystem: general updates for v5.2
Date: Tue, 7 May 2019 13:35:39 +1000 (AEST) [thread overview]
Message-ID: <alpine.LRH.2.21.1905071333580.5714@namei.org> (raw)
Just a few bugfixes and documentation updates.
Please pull.
The following changes since commit 8c2ffd9174779014c3fe1f96d9dc3641d9175f00:
Linux 5.1-rc2 (2019-03-24 14:02:26 -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 6beff00b79ca0b5caf0ce6fb8e11f57311bd95f8:
seccomp: fix up grammar in comment (2019-04-23 16:21:12 -0700)
----------------------------------------------------------------
Denis Efremov (11):
LSM: fix documentation for sb_copy_data hook
LSM: fix documentation for the syslog hook
LSM: fix documentation for the socket_post_create hook
LSM: fix documentation for the task_setscheduler hook
LSM: fix documentation for the socket_getpeersec_dgram hook
LSM: fix documentation for the path_chmod hook
LSM: fix documentation for the audit_* hooks
LSM: fix documentation for the msg_queue_* hooks
LSM: fix documentation for the sem_* hooks
LSM: fix documentation for the shm_* hooks
LSM: lsm_hooks.h: fix documentation format
James Morris (2):
Merge tag 'v5.1-rc2' into next-general
Revert "security: inode: fix a missing check for securityfs_create_file"
Jann Horn (3):
Yama: mark local symbols as static
security: don't use RCU accessors for cred->session_keyring
keys: safe concurrent user->{session,uid}_keyring access
Kangjie Lu (1):
security: inode: fix a missing check for securityfs_create_file
Mukesh Ojha (1):
Yama: mark function as static
Tycho Andersen (1):
seccomp: fix up grammar in comment
include/linux/cred.h | 2 +-
include/linux/lsm_hooks.h | 170 +++++++++++++++++++++----------------------
include/linux/sched/user.h | 7 ++
kernel/seccomp.c | 2 +-
security/keys/process_keys.c | 41 +++++------
security/keys/request_key.c | 14 ++--
security/yama/yama_lsm.c | 8 +-
7 files changed, 119 insertions(+), 125 deletions(-)
next reply other threads:[~2019-05-07 3:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-07 3:35 James Morris [this message]
2019-05-07 17:20 ` [GIT PULL] Security subsystem: general updates for v5.2 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.1905071333580.5714@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