From: Kees Cook <keescook@chromium.org>
To: Guillaume Tucker <guillaume.tucker@collabora.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
David Laight <David.Laight@aculab.com>,
Arnd Bergmann <arnd@arndb.de>,
linux-kernel@vger.kernel.org, kernelci@groups.io,
linux-kselftest@vger.kernel.org, linux-hardening@vger.kernel.org,
Collabora Kernel ML <kernel@collabora.com>
Subject: Re: [PATCH 0/9] LKDTM: Improvements for kernelci.org
Date: Fri, 25 Jun 2021 23:12:46 -0700 [thread overview]
Message-ID: <202106252311.14501F2F@keescook> (raw)
In-Reply-To: <030c022b-985a-16eb-b9d7-73b6fed2d5a9@collabora.com>
On Fri, Jun 25, 2021 at 07:22:01AM +0100, Guillaume Tucker wrote:
> On 23/06/2021 21:39, Kees Cook wrote:
> > This is a bunch of LKDTM clean-ups to improve and expand testing,
> > given feedback from testing at kernelci.org. Adds a few new tests as
> > well.
> >
> > (If a pull-request is preferred, please let me know.)
> >
> > Thanks!
> >
> > -Kees
> >
> > Kees Cook (9):
> > selftests/lkdtm: Avoid needing explicit sub-shell
> > selftests/lkdtm: Fix expected text for CR4 pinning
> > selftests/lkdtm: Fix expected text for free poison
> > lkdtm/bugs: XFAIL UNALIGNED_LOAD_STORE_WRITE
> > lkdtm/heap: Add vmalloc linear overflow test
> > lkdtm: Enable DOUBLE_FAULT on all architectures
> > lkdtm: Add CONFIG hints in errors where possible
> > selftests/lkdtm: Enable various testable CONFIGs
> > lkdtm/heap: Add init_on_alloc tests
>
> Tested-by: "kernelci.org bot" <bot@kernelci.org>
>
>
> This whole series was tested on top of next-20210623, here are a
> couple of sample results from KernelCI staging:
>
> Clang 13 on AMD x86_64:
> https://staging.kernelci.org/test/plan/id/60d4a5ce3d2bc535d924bf25/
>
> GCC 8 on Intel x86_64:
> https://staging.kernelci.org/test/plan/id/60d570711a3d6beefe24bf26/
>
> And this is where the series was applied:
> https://github.com/kernelci/linux/commits/a9f4387015268e426c77fd51ed846c9756938828
Fantastic! Thanks; this looks great. :)
--
Kees Cook
prev parent reply other threads:[~2021-06-26 6:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-23 20:39 [PATCH 0/9] LKDTM: Improvements for kernelci.org Kees Cook
2021-06-23 20:39 ` [PATCH 1/9] selftests/lkdtm: Avoid needing explicit sub-shell Kees Cook
2021-06-23 20:39 ` [PATCH 2/9] selftests/lkdtm: Fix expected text for CR4 pinning Kees Cook
2021-06-23 20:39 ` [PATCH 3/9] selftests/lkdtm: Fix expected text for free poison Kees Cook
2021-06-23 20:39 ` [PATCH 4/9] lkdtm/bugs: XFAIL UNALIGNED_LOAD_STORE_WRITE Kees Cook
2021-06-23 20:39 ` [PATCH 5/9] lkdtm/heap: Add vmalloc linear overflow test Kees Cook
2021-06-23 20:39 ` [PATCH 6/9] lkdtm: Enable DOUBLE_FAULT on all architectures Kees Cook
2021-06-23 20:39 ` [PATCH 7/9] lkdtm: Add CONFIG hints in errors where possible Kees Cook
2021-06-23 20:39 ` [PATCH 8/9] selftests/lkdtm: Enable various testable CONFIGs Kees Cook
2021-06-23 20:39 ` [PATCH 9/9] lkdtm/heap: Add init_on_alloc tests Kees Cook
2021-06-24 13:32 ` [PATCH 0/9] LKDTM: Improvements for kernelci.org Greg Kroah-Hartman
2021-06-25 6:22 ` Guillaume Tucker
2021-06-26 6:12 ` Kees Cook [this message]
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=202106252311.14501F2F@keescook \
--to=keescook@chromium.org \
--cc=David.Laight@aculab.com \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=guillaume.tucker@collabora.com \
--cc=kernel@collabora.com \
--cc=kernelci@groups.io \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.