From: Kees Cook <keescook@chromium.org>
To: kernel test robot <oliver.sang@intel.com>
Cc: Guillaume Tucker <guillaume.tucker@collabora.com>,
David Laight <David.Laight@aculab.com>,
LKML <linux-kernel@vger.kernel.org>,
lkp@lists.01.org, lkp@intel.com
Subject: Re: [selftests/lkdtm] 7ecfffe9bc: kernel_BUG_at_drivers/misc/lkdtm/bugs.c
Date: Mon, 28 Jun 2021 08:07:02 -0700 [thread overview]
Message-ID: <202106280805.5620A53D08@keescook> (raw)
In-Reply-To: <20210628145922.GC22448@xsang-OptiPlex-9020>
On Mon, Jun 28, 2021 at 10:59:22PM +0800, kernel test robot wrote:
>
>
> Greeting,
>
> FYI, we noticed the following commit (built with gcc-9):
>
> commit: 7ecfffe9bcb6657ae3a86c58f8eae2fe37b54807 ("selftests/lkdtm: Avoid needing explicit sub-shell")
> https://git.kernel.org/cgit/linux/kernel/git/kees/linux.git for-next/lkdtm
>
>
> in testcase: kernel-selftests
> version: kernel-selftests-x86_64-f8879e85-1_20210621
> with following parameters:
>
> group: lkdtm
> ucode: 0xe2
>
> test-description: The kernel contains a set of "self tests" under the tools/testing/selftests/ directory. These are intended to be small unit tests to exercise individual code paths in the kernel.
> test-url: https://www.kernel.org/doc/Documentation/kselftest.txt
When running the "lkdtm" subsystem of tests, CI systems should ignore
console Oopses, since those are "working as intended" for lkdtm (which
is explicitly testing for those Oopses).
-Kees
--
Kees Cook
prev parent reply other threads:[~2021-06-28 15:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-28 14:59 [selftests/lkdtm] 7ecfffe9bc: kernel_BUG_at_drivers/misc/lkdtm/bugs.c kernel test robot
2021-06-28 15:07 ` 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=202106280805.5620A53D08@keescook \
--to=keescook@chromium.org \
--cc=David.Laight@aculab.com \
--cc=guillaume.tucker@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=lkp@lists.01.org \
--cc=oliver.sang@intel.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