From: Kees Cook <keescook@chromium.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org, Ard Biesheuvel <ardb@kernel.org>,
Arnd Bergmann <arnd@arndb.de>,
Christophe Leroy <christophe.leroy@csgroup.eu>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Kees Cook <keescook@chromium.org>,
Misono Tomohiro <misono.tomohiro@jp.fujitsu.com>,
Nathan Chancellor <nathan@kernel.org>,
Nick Desaulniers <ndesaulniers@google.com>
Subject: [GIT PULL] lkdtm updates for -next
Date: Thu, 16 Dec 2021 16:02:03 -0800 [thread overview]
Message-ID: <202112161601.DB11DD9@keescook> (raw)
Hi Greg,
Please pull these lkdtm updates for -next.
Thanks!
-Kees
The following changes since commit 136057256686de39cc3a07c2e39ef6bc43003ff6:
Linux 5.16-rc2 (2021-11-21 13:47:39 -0800)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git tags/lkdtm-v5.17-rc1
for you to fetch changes up to 90091c367e74d5b58d9ebe979cc363f7468f58d3:
selftest/lkdtm: Skip stack-entropy test if lkdtm is not available (2021-12-16 15:54:38 -0800)
----------------------------------------------------------------
lkdtm updates for v5.17-rc1
- Fix printk() usage during recursion (Ard Biesheuvel)
- Fix rodata section to actually have contents (Christophe Leroy)
- Add notes about lkdtm_kernel_info usage (Kees Cook)
- Avoid stack-entropy selftest when LKDTM is disabled (Misono Tomohiro)
----------------------------------------------------------------
Ard Biesheuvel (1):
lkdtm: avoid printk() in recursive_loop()
Christophe Leroy (1):
lkdtm: Fix content of section containing lkdtm_rodata_do_nothing()
Kees Cook (1):
lkdtm: Note that lkdtm_kernel_info should be removed in the future
Misono Tomohiro (1):
selftest/lkdtm: Skip stack-entropy test if lkdtm is not available
drivers/misc/lkdtm/Makefile | 2 +-
drivers/misc/lkdtm/bugs.c | 16 +++++++++-------
drivers/misc/lkdtm/core.c | 6 +++++-
tools/testing/selftests/lkdtm/stack-entropy.sh | 16 +++++++++++++++-
4 files changed, 30 insertions(+), 10 deletions(-)
--
Kees Cook
next reply other threads:[~2021-12-17 0:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-17 0:02 Kees Cook [this message]
2021-12-17 9:06 ` [GIT PULL] lkdtm updates for -next Greg Kroah-Hartman
-- strict thread matches above, loose matches on Subject: below --
2022-05-17 21:52 Kees Cook
2022-05-19 15:20 ` Greg Kroah-Hartman
2019-01-09 20:12 Kees Cook
2019-01-10 7:08 ` Greg Kroah-Hartman
2017-10-06 15:31 Kees Cook
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=202112161601.DB11DD9@keescook \
--to=keescook@chromium.org \
--cc=ardb@kernel.org \
--cc=arnd@arndb.de \
--cc=christophe.leroy@csgroup.eu \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=misono.tomohiro@jp.fujitsu.com \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
/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).