Re: issues with kmemleak backport

Chris Friesen
2010-01-21T15:39:39Z

On 01/20/2010 04:58 PM, Catalin Marinas wrote:
> Hi,
>
> First of all, apart from backporting the kmemleak patches I would
> suggest you do a kernel grep for kmemleak_* function calls as there may
> be explicit cases where allocated memory blocks are ignored from
> scanning (like the AGP aperture which is unmapped from the standard
> kernel linear mapping).

Thanks for the suggestion. I'll do that.

> Alternatively, until you get this to work, just modify kmemleak to dump
> information it has about every object it scans via dump_object_info()
> called from scan_object(). The amount of information is quite large but
> at least you should see the last block that it fails to scan and maybe
> add a kmemleak_ignore() on the block allocation site.

I finally got access to a 64-bit lab system and there the backport seems
to be working just fine. Since that's were I actually need it, life is
now much better. :)

If I run into more issues I'll try using your ideas to work around the
issue.

Thanks,

Chris