> On Dec 3, 2019, at 10:14 AM, Alexander Potapenko <glider@xxxxxxxxxx> wrote: > > Some tools are just not designed to work together. > For example, you won't be able to compile the kernel with both KASAN > and KMSAN enabled at the same time. > > Lockdep doesn't require any instrumentation to work, so it _might_ be > possible to make it work with KMSAN, but it will probably still slow > down the things to an unacceptable level. > I'm inclining towards disabling the two together for now, unless > anyone is willing to address that issue. > > Please let me know if you think I need to keep the link to > https://github.com/google/kmsan/issues/57 in the Kconfig comment, > right now it looks like: > > # KMSAN is currently incompatible with lockdep. Then, I don’t see much value with KMSAN get merged. Although In theory, it does cover a bit more than the existing memory debugging infrastructure, but the question is does it worth it? Maybe it needs more data to show a list of bugs it found that existing debugging options could not find?
