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: Thu, 7 Sep 2006 09:04:56 +0100 From: "Catalin Marinas" <catalin.marinas@...il.com> To: "Michal Piotrowski" <michal.k.k.piotrowski@...il.com> Cc: linux-kernel@...r.kernel.org Subject: Re: [PATCH 2.6.18-rc6 00/10] Kernel memory leak detector 0.10 On 07/09/06, Michal Piotrowski <michal.k.k.piotrowski@...il.com> wrote: > I get a kernel panic > http://www.stardust.webpages.pl/files/o_bugs/kmemleak-0.10/panic.jpg > > http://www.stardust.webpages.pl/files/o_bugs/kmemleak-0.10/kml-config Well, you set CONFIG_DEBUG_MEMLEAK_HASH_BITS to 32, this means that kmemleak needs to allocate (sizeof(void*) * 2^32) which is 16GB of RAM. I think a maximum of 20 should be enough (I got acceptable results with 16 hash bits, the default value, and it seemed to do better with 18). -- 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