| 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 13:41:44 -0400 From: "Fred Tyler" <fredty8@...il.com> To: vda.linux@...glemail.com, linux-kernel@...r.kernel.org Subject: Re: Slow, persistent memory leak in 2.6.20 On 8/26/07, Denys Vlasenko <vda.linux@...glemail.com> wrote: > On Sunday 26 August 2007 17:16, Fred Tyler wrote: > > So, I guess it worked? (I don't know what was supposed to happen, but > > memory usage dropped significantly when I did this.) > > If you can reclaim "leaked" memory this way, it means that > you found a bug where cached data is incorrectly kept > in RAM in preference of other data. > (I'm assuming that you do have real problems after some time > of "leaking" memory - you mention that you get swap storms > and eventually machine is dead.) This was exactly what happened with 2.6.12 -- more and more memory used until there was a swap storm and a dead machine. The 2.6.20 machines haven't been up long enough to know if they're going to be hit by the same problem, but it seems peculiar to me that the 2.6.16 machine does not do anything remotely like this. As you can see in the graphs, the 2.6.16 memory use levels off very quickly, but 2.6.12 keeps dropping until the machine bombs. The 2.6.20 graph looks like it's heading the same direction as 2.6.12. I'm going to run drop_caches on the 2.6.20 machines tonight and see what happens... - 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