On Mon, Dec 11, 2023 at 7:59 PM Paul Heidekrüger <paul.heidekrueger@xxxxxx> wrote: > > > Hi Paul, > > > > I've been successfully running KASAN tests with CONFIG_TRACEPOINTS > > enabled on arm64 since this patch landed. > > Interesting ... > > > What happens when you try running the tests with .kunitconfig? Does > > CONFIG_TRACEPOINTS or CONFIG_KASAN_KUNIT_TEST get disabled during > > kernel building? > > Yes, exactly, that's what's happening. > > Here's the output kunit.py is giving me. I replaced CONFIG_DEBUG_KERNEL with > CONFIG_TRACEPOINTS in my .kunitconfig. Otherwise, it's identical with the one I > posted above. > > ➜ ./tools/testing/kunit/kunit.py run --kunitconfig=mm/kasan/.kunitconfig --arch=arm64 > Configuring KUnit Kernel ... > Regenerating .config ... > Populating config with: > $ make ARCH=arm64 O=.kunit olddefconfig > ERROR:root:Not all Kconfig options selected in kunitconfig were in the generated .config. > This is probably due to unsatisfied dependencies. > Missing: CONFIG_KASAN_KUNIT_TEST=y, CONFIG_TRACEPOINTS=y > > Does CONFIG_TRACEPOINTS have some dependency I'm not seeing? I couldn't find a > reason why it would get disabled, but I could definitely be wrong. Does your .kunitconfig include CONFIG_TRACEPOINTS=y? I don't see it in the listing that you sent earlier.
