| 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: <6bffcb0e0609070235v6309595fgecb1880eb3185841@mail.gmail.com> Date: Thu, 7 Sep 2006 11:35:50 +0200 From: "Michal Piotrowski" <michal.k.k.piotrowski@...il.com> To: "Catalin Marinas" <catalin.marinas@...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, Catalin Marinas <catalin.marinas@...il.com> wrote: > On 07/09/06, Michal Piotrowski <michal.k.k.piotrowski@...il.com> wrote: > > On 07/09/06, Catalin Marinas <catalin.marinas@...il.com> wrote: > > > Have you tried 16? > > > > No, I haven't. With DEBUG_MEMLEAK_HASH_BITS=16 system woks fine. > > 8 hash bits would lead to a really slow hash table lookup since you > would only have 256 entries and it uses linked lists to deal with > collisions (you may have tens of thousands of pointers to be stored in > the hash). Anyway, I attach a patch which allows you to set small > values but it is highly unrecommended. How about documeting maxial "safe" values? Something like "If you have X MB/GB of RAM memory you can set Y X | Y 256 MB | 25 512 MB | 26 1GB | 27 2GB | 28 4GB | 29" > > -- > Catalin > Regards, Michal -- Michal K. K. Piotrowski LTG - Linux Testers Group (http://www.stardust.webpages.pl/ltg/) - 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