Messages in this thread | | | Date | Tue, 25 Aug 2009 10:48:08 +0200 | From | Ingo Molnar <> | Subject | Re: WARNING: kmemcheck: Caught 32-bit read from uninitialized memory (f6f6e1a4), by kmemleak's scan_block() |
| |
* Pekka Enberg <penberg@cs.helsinki.fi> wrote:
> On Tue, 2009-08-25 at 10:32 +0200, Ingo Molnar wrote: > > > In any case, I don't think it is very productive to run them both > > > at the same time, simply because kmemcheck slows every memory > > > access down so much and scanning memory doesn't exactly help that. > > > It _could_ be useful to have them compiled into the same kernel, > > > though, e.g. a distro "-debug" kernel. > > > > > > Maybe you can just add the "depends on !KMEMLEAK" to > > > CONFIG_KMEMCHECK in tip/out-of-tree for now? > > > > i think it would be far more intelligent to annotate those accesses > > by kmemleak as 'trust me, dont check'. Willing to test such a patch. > > I guess something like this totally untested patch should do it. > Vegard, Catalin?
Looks good - but doesnt apply cleanly to -tip because i picked up a number of kmemleak patches into tip:out-of-tree for testing - so i'll leave it up for Vegard/Catalin to do a blessed version of it against the kmemleak tree - which i hope will apply fine to tip too :)
Ingo
| |