From: Kees Cook <keescook@chromium.org>
To: James Morris <jmorris@namei.org>
Cc: linux-kernel@vger.kernel.org,
Casey Schaufler <casey@schaufler-ca.com>,
John Johansen <john.johansen@canonical.com>,
linux-security-module@vger.kernel.org
Subject: [GIT PULL] loadpin updates for security-next
Date: Thu, 18 Oct 2018 16:05:42 -0700 [thread overview]
Message-ID: <20181018230542.GA48284@beast> (raw)
Hi James,
Please pull these loadpin changes for security-next. 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).
Thanks!
-Kees
The following changes since commit 57361846b52bc686112da6ca5368d11210796804:
Linux 4.19-rc2 (2018-09-02 14:37:30 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git tags/loadpin-security-next
for you to fetch changes up to 13523bef1e2154b6d02836cd0f6c0ffc89b2eae6:
LoadPin: Rename boot param "enabled" to "enforce" (2018-10-18 15:29:44 -0700)
----------------------------------------------------------------
LoadPin: report improvement and parameter renaming
- Report human-readable device name during init
- Change boot parameter and Kconfig "enabled" to "enforce"
----------------------------------------------------------------
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(-)
--
Kees Cook
Pixel Security
next reply other threads:[~2018-10-18 23:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-18 23:05 Kees Cook [this message]
2018-10-19 0:21 ` [GIT PULL] loadpin updates for security-next James Morris
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=20181018230542.GA48284@beast \
--to=keescook@chromium.org \
--cc=casey@schaufler-ca.com \
--cc=jmorris@namei.org \
--cc=john.johansen@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.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).