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
| ||
|
Date: Fri, 12 Feb 2010 17:50:31 +0000 From: Catalin Marinas <catalin.marinas@....com> To: Minchan Kim <minchan.kim@...il.com> Cc: Chris Friesen <cfriesen@...tel.com>, KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>, Rik van Riel <riel@...hat.com>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, linux-mm@...ck.org, Balbir Singh <balbir@...ux.vnet.ibm.com> Subject: Re: tracking memory usage/leak in "inactive" field in /proc/meminfo? Minchan Kim <minchan.kim@...il.com> wrote: > On Fri, Feb 12, 2010 at 3:54 AM, Chris Friesen <cfriesen@...tel.com> wrote: >> I have a modified version of that which I picked up as part of the >> kmemleak backport. However, it doesn't help unless I can narrow down >> *which* pages I should care about. > > kmemleak doesn't support page allocator and ioremap. > Above URL patch just can tell who requests page which is using(ie, not > free) now. The ioremap can be easily tracked by kmemleak (it is on my to-do list but haven't managed to do it yet). That's not far from vmalloc. The page allocator is a bit more difficult since it's used by the slab allocator as well and it may lead to some recursive calls into kmemleak. I'll have a think. Anyway, you can leak memory without this being detected by kmemleak - just add the allocated objects to a list and never remove them. -- Catalin -- 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