On Fri, Dec 20, 2019 at 07:49:13PM +0100, glider@xxxxxxxxxx wrote: > KernelMemorySanitizer (KMSAN) is a detector of errors related to uses of > uninitialized memory. It relies on compile-time Clang instrumentation > (similar to MSan in the userspace: > https://clang.llvm.org/docs/MemorySanitizer.html) > and tracks the state of every bit of kernel memory, being able to report > an error if uninitialized value is used in a condition, dereferenced or > copied to userspace, USB or network. > <..> > > 2. checkpatch.pl complains a lot about the use of BUG_ON in KMSAN > source. I don't have a strong opinion on this, but KMSAN is a debugging > tool, so any runtime invariant violation in it renders the tool useless. > Therefore it doesn't make much sense to not terminate after a bug in > KMSAN. Such early termination will cause hard time for verification teams execute any major test suite with KMSAN till it will be without any bugs. So yes, I think that the best solution is to avoid BUG_ONs in non-critical code. Thanks
