From: Kees Cook <keescook@chromium.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>,
Matthew Wilcox <willy@infradead.org>,
Kees Cook <keescook@chromium.org>,
Muhammad Usama Anjum <usama.anjum@collabora.com>
Subject: [GIT PULL] lkdtm updates for -next
Date: Tue, 17 May 2022 14:52:58 -0700 [thread overview]
Message-ID: <202205171451.EE8E27685@keescook> (raw)
Hi Greg,
Please pull these lkdtm updates for -next (preferably for the coming
merge window).
Thanks!
-Kees
The following changes since commit 2a0338769f27a38b5dd60b6bef5b83003789439b:
lkdtm: cfi: Fix type width for masking PAC bits (2022-04-26 17:11:05 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git tags/lkdtm-next
for you to fetch changes up to f260fd59e3f387432bda51072fff4494fba10b91:
lkdtm/heap: Hide allocation size from -Warray-bounds (2022-05-17 14:47:08 -0700)
----------------------------------------------------------------
lkdtm updates for -next
- Test for new usercopy memory regions
- avoid GCC 12 warnings
- update expected CONFIGs for selftests
----------------------------------------------------------------
Kees Cook (3):
lkdtm/usercopy: Rename "heap" to "slab"
lkdtm/usercopy: Check vmalloc and >0-order folios
lkdtm/heap: Hide allocation size from -Warray-bounds
Muhammad Usama Anjum (1):
selftests/lkdtm: Add configs for stackleak and "after free" tests
drivers/misc/lkdtm/heap.c | 1 +
drivers/misc/lkdtm/usercopy.c | 113 +++++++++++++++++++++++++++-----
tools/testing/selftests/lkdtm/config | 2 +
tools/testing/selftests/lkdtm/tests.txt | 8 +--
4 files changed, 105 insertions(+), 19 deletions(-)
--
Kees Cook
next reply other threads:[~2022-05-17 21:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-17 21:52 Kees Cook [this message]
2022-05-19 15:20 ` Greg Kroah-Hartman
-- strict thread matches above, loose matches on Subject: below --
2021-12-17 0:02 Kees Cook
2021-12-17 9:06 ` 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=202205171451.EE8E27685@keescook \
--to=keescook@chromium.org \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=usama.anjum@collabora.com \
--cc=willy@infradead.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
all inboxes | Powered by JetHome®