From: Shuah Khan <skhan@linuxfoundation.org>
To: "Mickaël Salaün" <mic@digikod.net>,
"Brendan Higgins" <brendanhiggins@google.com>,
"David Gow" <davidgow@google.com>, "Rae Moar" <rmoar@google.com>
Cc: Alan Maguire <alan.maguire@oracle.com>,
Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
"Eric W . Biederman" <ebiederm@xmission.com>,
"H . Peter Anvin" <hpa@zytor.com>, Ingo Molnar <mingo@redhat.com>,
James Morris <jamorris@linux.microsoft.com>,
Kees Cook <keescook@chromium.org>,
Luis Chamberlain <mcgrof@kernel.org>,
"Madhavan T . Venkataraman" <madvenka@linux.microsoft.com>,
Marco Pagani <marpagan@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Sean Christopherson <seanjc@google.com>,
Stephen Boyd <sboyd@kernel.org>,
Thara Gopinath <tgopinath@microsoft.com>,
Thomas Gleixner <tglx@linutronix.de>,
Vitaly Kuznetsov <vkuznets@redhat.com>,
Zahra Tarkhani <ztarkhani@microsoft.com>,
kunit-dev@googlegroups.com, kvm@vger.kernel.org,
linux-hardening@vger.kernel.org, linux-hyperv@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
linux-security-module@vger.kernel.org,
linux-um@lists.infradead.org, x86@kernel.org,
Shuah Khan <skhan@linuxfoundation.org>
Subject: Re: [PATCH v4 RESEND 0/7] Handle faults in KUnit tests
Date: Tue, 9 Apr 2024 11:28:06 -0600 [thread overview]
Message-ID: <5a04e40c-daba-4a1d-b5db-f70d2e51c403@linuxfoundation.org> (raw)
In-Reply-To: <20240408074625.65017-1-mic@digikod.net>
On 4/8/24 01:46, Mickaël Salaün wrote:
> Hi,
>
> This patch series teaches KUnit to handle kthread faults as errors, and
> it brings a few related fixes and improvements.
>
> Shuah, everything should be OK now, could you please merge this series?
>
> All these tests pass (on top of v6.8):
> ./tools/testing/kunit/kunit.py run --alltests
> ./tools/testing/kunit/kunit.py run --alltests --arch x86_64
> ./tools/testing/kunit/kunit.py run --alltests --arch arm64 \
> --cross_compile=aarch64-linux-gnu-
>
> I also built and ran KUnit tests as a kernel module.
>
> A new test case check NULL pointer dereference, which wasn't possible
> before.
>
> This is useful to test current kernel self-protection mechanisms or
> future ones such as Heki: https://github.com/heki-linux
>
> Previous versions:
> v3: https://lore.kernel.org/r/20240319104857.70783-1-mic@digikod.net
> v2: https://lore.kernel.org/r/20240301194037.532117-1-mic@digikod.net
> v1: https://lore.kernel.org/r/20240229170409.365386-1-mic@digikod.net
>
> Regards,
>
> Mickaël Salaün (7):
> kunit: Handle thread creation error
> kunit: Fix kthread reference
> kunit: Fix timeout message
> kunit: Handle test faults
> kunit: Fix KUNIT_SUCCESS() calls in iov_iter tests
> kunit: Print last test location on fault
> kunit: Add tests for fault
>
Thank you for the resend. Applied to linux-kselftest kunit branch
for Linux 6.10-rc1.
thanks,
-- Shuah
prev parent reply other threads:[~2024-04-09 17:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-08 7:46 [PATCH v4 RESEND 0/7] Handle faults in KUnit tests Mickaël Salaün
2024-04-08 7:46 ` [PATCH v4 RESEND 1/7] kunit: Handle thread creation error Mickaël Salaün
2024-04-08 7:46 ` [PATCH v4 RESEND 2/7] kunit: Fix kthread reference Mickaël Salaün
2024-04-08 7:46 ` [PATCH v4 RESEND 3/7] kunit: Fix timeout message Mickaël Salaün
2024-04-08 7:46 ` [PATCH v4 RESEND 4/7] kunit: Handle test faults Mickaël Salaün
2024-04-08 7:46 ` [PATCH v4 RESEND 5/7] kunit: Fix KUNIT_SUCCESS() calls in iov_iter tests Mickaël Salaün
2024-04-08 7:46 ` [PATCH v4 RESEND 6/7] kunit: Print last test location on fault Mickaël Salaün
2024-04-08 7:46 ` [PATCH v4 RESEND 7/7] kunit: Add tests for fault Mickaël Salaün
2024-04-09 17:28 ` Shuah Khan [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=5a04e40c-daba-4a1d-b5db-f70d2e51c403@linuxfoundation.org \
--to=skhan@linuxfoundation.org \
--cc=alan.maguire@oracle.com \
--cc=bp@alien8.de \
--cc=brendanhiggins@google.com \
--cc=dave.hansen@linux.intel.com \
--cc=davidgow@google.com \
--cc=ebiederm@xmission.com \
--cc=hpa@zytor.com \
--cc=jamorris@linux.microsoft.com \
--cc=keescook@chromium.org \
--cc=kunit-dev@googlegroups.com \
--cc=kvm@vger.kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=linux-um@lists.infradead.org \
--cc=madvenka@linux.microsoft.com \
--cc=marpagan@redhat.com \
--cc=mcgrof@kernel.org \
--cc=mic@digikod.net \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=rmoar@google.com \
--cc=sboyd@kernel.org \
--cc=seanjc@google.com \
--cc=tglx@linutronix.de \
--cc=tgopinath@microsoft.com \
--cc=vkuznets@redhat.com \
--cc=x86@kernel.org \
--cc=ztarkhani@microsoft.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 read-only IMAP folder(s) and NNTP newsgroup(s).