RE: [PATCH 0/7] Silence spurious warnings and crashes from kunit test suites

From: Justin He

Date: Thu May 14 2026 - 03:19:05 EST




> -----Original Message-----
> From: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
> Sent: Thursday, May 14, 2026 3:02 PM
> To: Justin He <Justin.He@xxxxxxx>
> Cc: linux-kernel@xxxxxxxxxxxxxxx; linux-fsdevel@xxxxxxxxxxxxxxx; linux-perf-
> users@xxxxxxxxxxxxxxx; linux-kselftest@xxxxxxxxxxxxxxx; kunit-
> dev@xxxxxxxxxxxxxxxx; kasan-dev@xxxxxxxxxxxxxxxx; linux-
> mm@xxxxxxxxx; Arnd Bergmann <arnd@xxxxxxxx>; Alexander Viro
> <viro@xxxxxxxxxxxxxxxxxx>; Christian Brauner <brauner@xxxxxxxxxx>; Jan Kara
> <jack@xxxxxxx>; Peter Zijlstra <peterz@xxxxxxxxxxxxx>; Ingo Molnar
> <mingo@xxxxxxxxxx>; Arnaldo Carvalho de Melo <acme@xxxxxxxxxx>;
> Namhyung Kim <namhyung@xxxxxxxxxx>; Mark Rutland
> <Mark.Rutland@xxxxxxx>; Alexander Shishkin
> <alexander.shishkin@xxxxxxxxxxxxxxx>; Jiri Olsa <jolsa@xxxxxxxxxx>; Ian
> Rogers <irogers@xxxxxxxxxx>; Adrian Hunter <adrian.hunter@xxxxxxxxx>;
> James Clark <james.clark@xxxxxxxxxx>; Brendan Higgins
> <brendan.higgins@xxxxxxxxx>; David Gow <david@xxxxxxxxxxxx>; Rae Moar
> <raemoar63@xxxxxxxxx>; Alexander Potapenko <glider@xxxxxxxxxx>;
> Marco Elver <elver@xxxxxxxxxx>; Dmitry Vyukov <dvyukov@xxxxxxxxxx>;
> Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>; Paul E. McKenney
> <paulmck@xxxxxxxxxx>; Petr Mladek <pmladek@xxxxxxxx>; Kees Cook
> <kees@xxxxxxxxxx>; David Disseldorp <ddiss@xxxxxxx>
> Subject: Re: [PATCH 0/7] Silence spurious warnings and crashes from kunit
> test suites
>
> On Thu, May 14, 2026 at 05:04:48AM +0000, Jia He wrote:
> > Running the full kunit suite on arm64 (128-core Neoverse N2) with
> > 7.1-rc3+ produces a handful of backtraces that are not real kernel
> > bugs but rather test-infrastructure issues: races with boot-time code,
> > missing bounds checks, resource leaks, and sysfs duplicate-name splats.
> >
> > This series fixes them one by one so that a clean kunit run no longer
> > leaves noise in dmesg:
>
> This series was sent to too many different people at once. Always break your
> changes up into subsystem-specific series as no one can take all of these
> through their tree, and our tools, as you know, have a hard time of just
> picking one patch out of a series.
>
Ok, thanks for the feedback. I understand the concern.
I’ll split the changes into subsystem‑specific series and resend them accordingly.

---
Cheers,
Justin He(Jia He)