[PATCH v9 0/4] kunit: Add support for suppressing warning backtraces
Albert Esteve
aesteve at redhat.com
Tue May 12 08:05:18 PDT 2026
On Sat, May 9, 2026 at 1:52 AM Andrew Morton <akpm at linux-foundation.org> wrote:
>
> On Fri, 08 May 2026 17:02:44 +0200 Albert Esteve <aesteve at redhat.com> wrote:
>
> > Some unit tests intentionally trigger warning backtraces by passing bad
> > parameters to kernel API functions. Such unit tests typically check the
> > return value from such calls, not the existence of the warning backtrace.
> >
> > ...
> >
> > Solve the problem by providing a means to suppress warning backtraces
> > originating from the current kthread while executing test code.
> > Since each KUnit test runs in its own kthread, this effectively scopes
> > suppression to the test that enabled it, without requiring any
> > architecture-specific code.
>
> Thanks. AI review has a bunch of questions:
> https://sashiko.dev/#/patchset/20260508-kunit_add_support-v9-0-99df7aa880f6@redhat.com
>
Hi! Most look like valid concerns/issues. I will send a new version
addressing them then, and monitor sashiko to ensure I clear
everything.
Thanks for the link.
BR,
Albert.
More information about the linux-riscv
mailing list