From: James Morris <jmorris@namei.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-security-module@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] security: LoadPin changes for v4.20
Date: Thu, 25 Oct 2018 20:39:35 +1100 (AEDT) [thread overview]
Message-ID: <alpine.LRH.2.21.1810252038150.30470@namei.org> (raw)
Please pull.
From Kees: "This is a small reporting improvement and the param change
needed for the ordering series (but since the loadpin change is desired
and separable, I'm putting it here)."
---
The following changes since commit 3f6caaf5ff33073ca1a3a0b82edacab3c57c38f9:
LSM: Don't ignore initialization failures (2018-10-10 20:40:22 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/linux-security.git next-loadpin
for you to fetch changes up to 85a585918fb4122ad26b6febaec5c3c90bf2535c:
Merge tag 'loadpin-security-next' of https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux into next-loadpin (2018-10-18 17:20:08 -0700)
----------------------------------------------------------------
James Morris (1):
Merge tag 'loadpin-security-next' of https://git.kernel.org/.../kees/linux into next-loadpin
Kees Cook (2):
LoadPin: Report friendly block device name
LoadPin: Rename boot param "enabled" to "enforce"
security/loadpin/Kconfig | 4 ++--
security/loadpin/loadpin.c | 26 +++++++++++++++-----------
2 files changed, 17 insertions(+), 13 deletions(-)
next reply other threads:[~2018-10-25 9:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-25 9:39 James Morris [this message]
2018-10-25 20:32 ` [GIT PULL] security: LoadPin changes for v4.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.1810252038150.30470@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).