Thanks for the catch.
Should be addressed by
https://lore.kernel.org/linux-kselftest/20210406172901.1729216-1-dlaty...@google.com/
When I was testing the CONFIG_KUNIT=n case, I added it to a file that
wasn't being compiled (CONFIG_UBSAN=y is not sufficient for
lib/ubsan.c to be compiled...).
On Tue, Apr 6, 2021 at 3:24 AM Stephen Rothwell <s...@canb.auug.org.au> wrote:
>
> Hi all,
>
> After merging the kunit-next tree, today's linux-next build (x86_64
> allmodconfig) produced this warning:
>
> In file included from lib/kunit/test.c:10:
> include/kunit/test-bug.h:22:28: warning: '__kunit_fail_current_test' defined
> but not used [-Wunused-function]
> 22 | static __printf(3, 4) void __kunit_fail_current_test(const char
> *file, int line,
> | ^~~~~~~~~~~~~~~~~~~~~~~~~
>
> Introduced by commit
>
> 359a376081d4 ("kunit: support failure from dynamic analysis tools")
>
> --
> Cheers,
> Stephen Rothwell
