| 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: Tue, 4 Oct 2011 21:50:26 +0100 From: Catalin Marinas <catalin.marinas@....com> To: Nick Bowler <nbowler@...iptictech.com> Cc: linux-kernel@...r.kernel.org Subject: Re: [PATCH 4/4] kmemleak: Report previously found leaks even after an error On 4 October 2011 18:45, Nick Bowler <nbowler@...iptictech.com> wrote: > On 2011-09-29 12:02 +0100, Catalin Marinas wrote: >> If an error fatal to kmemleak (like memory allocation failure) happens, >> kmemleak disables itself but it also removes the access to any >> previously found memory leaks. This patch allows read-only access to the >> kmemleak debugfs interface but disables any other action. >> >> Repored-by: Nick Bowler <nbowler@...iptictech.com> > > Reported-by: ... I was wondering why you were not automatically cc'ed. >> Signed-off-by: Catalin Marinas <catalin.marinas@....com> > > Cool, I'll try this out. Kmemleak rarely stays alive for more than a > few days on my desktop before shutting itself down due to an allocation > failure, so this should be really handy. You can have a look at /proc/slabinfo and meminfo and see if there are any really big leaks. In general the kmemleak objects number is higher than the sum of all the other slab objects (but I haven't done any statistics). Hopefully kmemleak doesn't leak memory :) (I should add some simple checks though). -- 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