On Tue, 15 Sep 2020 at 23:28, Josh Poimboeuf <jpoim...@redhat.com> wrote: > On Tue, Sep 15, 2020 at 02:13:01PM -0700, Nick Desaulniers wrote: > > Triple checking what I wrote above; it looks like the randconfig had > > BOTH CONFIG_KASAN=y and CONFIG_UBSAN=y enabled. Aren't the sanitizers > > supposed to be mutually exclusive? If so, we should ensure that via > > kconfig these can't be selected together via randconfig. > > No idea...
They are not mutually exclusive. The big ones like KASAN/KCSAN/KMSAN are mutually exclusive (compiler complains if you mix the flags), but UBSAN can be enabled with other sanitizers (and fsanitize-coverage, although not strictly a "sanitizer" it's still instrumentation based). In general, we shouldn't artificially disallow mixing them if it's supported by the compiler and our runtime can handle it. I'll have a look at the rest tomorrow (UBSAN_TRAP stuff, which coincidentally also came up in some other patch). Thanks, -- Marco
