On Wed, Oct 1, 2014 at 6:11 PM, Andrey Ryabinin <[email protected]> wrote: >>>>>>> >>>>>>> We can disable kasan instrumentation of this file as well. >>>>>> >>>>>> Yes, but why? I don't think we need that. >>>>> >>>>> Just gut feeling. Such tools usually don't play well together. For >>>>> example, due to asan quarantine lots of leaks will be missed (if we >>>>> pretend that tools work together, end users will use them together and >>>>> miss bugs). I won't be surprised if leak detector touches freed >>>>> objects under some circumstances as well. >>>>> We can do this if/when discover actual compatibility issues, of course. >>>> >>>> I think it's worth testing them together first. >>>> >>> >>> I did test them together. With this patch applied both tools works without >>> problems. >> >> What do you mean "works without problems"? Are you sure that kmemleak >> still detects all leaks it is intended to detect? >> > > Yes I'm sure about that. And how kasan could affect on kmemleak's capability > to detect leaks?
Ah, OK, we don't have quarantine. The idea is that redzones and quarantine will contain parasitical pointers (quarantine is exactly a linked list of freed objects). -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
