Memory leak with dev_add_pack()
From: Spiro Trikaliotis <hidden>
Date: 2011-01-23 10:40:04
Hallo Michi, first of all, thank you for your answer. * On Sat, Jan 22, 2011 at 08:18:05AM +0100 Michael Blizek wrote:
On 21:54 Fri 21 Jan , Spiro Trikaliotis wrote:
- Does this also happen, if you do not call PromiscuousMode_Enter?
Yes, it does. In fact, I only included it in my minimal example so the memory leak happens faster, in case someone wants to give it a try himself.
- Which user grows is /proc/slabinfo? (If this file is emply or does not exist, you may meed to recompile the kernel to use slab instead of sl[b-z]b)
Thank you for the pointer, it might help. The objects which have changed the most on a mildly loaded network are: 25000 buffer_head 5000 dentry 5000 ext3_inode_cache 5000 size-64 The number if the number of more active object after approx. 20h of letting it run on the mildly loaded network. Note that the ext3_inode_cache might have grown because I was regularly writing a new log file from slabinfo (slabinfo --once > slabinfo.`date +...`) Thus, I would expect I am leaking buffer_head.
- Which kernel version are you using? Have you tried different versions?
I am running this on a Debian Lenny (32 bit), Kernel 2.6.26-2-686, and an Ubuntu 10.04, also 32 bit. Unfortunately this machine is currently out of my reach, but I think it is a variant of 2.6.32 or 2.6.33. Both kernels are from the distribution, that is, no vanilla kernels. Beste Gr??e Spiro. -- Spiro R. Trikaliotis http://opencbm.sf.net/ http://www.trikaliotis.net/ http://www.viceteam.org/