| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <4B58740F.7050400@nortel.com> Date: Thu, 21 Jan 2010 09:34:39 -0600 From: "Chris Friesen" <cfriesen@...tel.com> To: Catalin Marinas <catalin.marinas@....com> CC: Linux kernel <linux-kernel@...r.kernel.org> Subject: Re: issues with kmemleak backport 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 -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists