On Tue, Mar 05, 2024 at 10:40:28AM -0800, Guenter Roeck 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.
>
> Such in
Hi Daniel,
On 3/6/24 10:24, Daniel Díaz wrote:
[ ... ]
Thank you SO very much for this work! This is very much appreciated!
Thanks a lot for the feedback.
We run into these warnings at LKFT all the time, and making sure that
the noise doesn't drown the relevant signal is very important.
Hello!
On Tue, 5 Mar 2024 at 12:40, Guenter Roeck 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.
>
> Such intenti
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.
Such intentionally generated warning backtraces are neither desirable
nor useful
