>
>
>
>
>> May I ask what is the purpose of the config in question?
>>
> it's what I use on my home desktop PC(but merged the laptop .config into
> it, didn't have the time to test it on laptop so far yet) and I've enabled
> all tests to catch things early in the hopes of avoiding some potential
> btrfs filesystem corruption(for a third time, so far) if nothing else...
> but otherwise it'd be just reassuring to know that things are performing
> within their expected parameters (with tests passing and all). I don't
> remember why I've tried to keep modules at a minimum though.
>

I see, thanks for the explanation.
I think many tests in lib/ may produce strange warnings that are meant to
be parsed by human devs that know what to expect.
It would be nice to have them converted to KUNIT, but that's a long way to
go.