| 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: Sun, 26 Aug 2007 19:32:01 +0400 From: Alexey Dobriyan <adobriyan@...il.com> To: Fred Tyler <fredty8@...il.com> Cc: linux-kernel@...r.kernel.org Subject: Re: Slow, persistent memory leak in 2.6.20 On Sun, Aug 26, 2007 at 10:39:11AM -0400, Fred Tyler wrote: > I think I've come across a memory leak in 2.6.20. I've upgraded to the > latest 2.6.20.17, but it didn't seem to help. > > A little background: I saw something exactly like this many months ago > with a 2.6.12 kernel. However, by 2.6.16.x the leak had apparently > been fixed, so I didn't pursue it. I just assumed it had been fixed. > But either it remains in 2.6.20 or else a new leak has appeared. > > FWIW, this is an x86_64 machine, but I also saw nearly the same > behavior on a i386 machine running 2.6.12. (Links to graphs showing > long-term memory usage are at the bottom of this email if you want to > skip all the text stats in the middle.) > > Immediately after booting the system, I shut down all services to get > a baseline for comparison. Here is the output of top and vmstat with > virtually nothing running: You can try "Kernel Hacking" => "Debug slab memory allocations" => "Memory leak debugging". After you think it leaked pretty much, post output of sort -n -k2 /proc/slab_allocators - 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