From mboxrd@z Thu Jan  1 00:00:00 1970
From: michi1@michaelblizek.twilightparadox.com (Michael Blizek)
Date: Sat, 22 Jan 2011 08:18:05 +0100
Subject: Memory leak with dev_add_pack()
In-Reply-To: <20110121205402.GA3915@trikaliotis.net>
References: <20110121205402.GA3915@trikaliotis.net>
Message-ID: <20110122071805.GB2047@michaelblizek.twilightparadox.com>
To: kernelnewbies@lists.kernelnewbies.org
List-Id: kernelnewbies.lists.kernelnewbies.org

Hi!

On 21:54 Fri 21 Jan     , Spiro Trikaliotis wrote:
...
> While it essentially works as I want it to, I found that I am leaking
> memory this way. Having this module in a highly loaded network, 
> "head -n5 /proc/meminfo" shows that MemFree is steadily falling, until
> the kernel OOPS with an out of memory condition.

I could not see anything wrong here either. Some things which came to my
mind where:

- Does this also happen, if you do not call PromiscuousMode_Enter?
- 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)
- Which kernel version are you using? Have you tried different versions?

	-Michi
-- 
programing a layer 3+4 network protocol for mesh networks
see http://michaelblizek.twilightparadox.com