On Fri, 08 May 2026 17:02:44 +0200 Albert Esteve <[email protected]> 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/[email protected]
