From: Willy Tarreau <w@1wt.eu>
To: linux-kernel@vger.kernel.org
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: ip_conntrack_core - possible memory leak in 2.4
Date: Thu, 5 Oct 2006 21:30:28 +0200 [thread overview]
Message-ID: <20061005193028.GC5050@1wt.eu> (raw)
In-Reply-To: <20061004180201.GA18386@nomi.cz>
[netfilter-devel list CC'd]
Hello,
On Wed, Oct 04, 2006 at 08:02:01PM +0200, onovy@nomi.cz wrote:
> hi,
>
> i have there MontaVista based router, with 2.4.17_mvl21-malta-mips_fp_le
> kernel. I think, there is memory leak in ip_conntrack code. There are
> eta 500 conntrack connection all the time. But after some day i get
> "ip_conntrack: table full" in kmsg.
> /proc/sys/net/ipv4/netfilter/ip_conntrack_max have 3072 value.
> grep ip_conntrack /proc/slabinfo
> ip_conntrack 3006 3250 384 319 325 1
> ^^ there are 3006 allocated conntracks
> cat /proc/net/ip_conntrack | wc -l
> 30
> ^^ in table are only 30 lines.
>
> Acording to this:
> http://lists.netfilter.org/pipermail/netfilter-devel/2004-May/015628.html
> i don't think, this is fixed in 2.4 tree, but i can't test it with newer
> version.
Well, I know several old 2.4 netfilter systems running around and which
process between 100 and 200 millions of sessions a day with peak hours
around 4000 sessions/s. They might have been rebooted twice in 3 years,
and they still work without a glitch. So I clearly don't think that the
problem mentionned above is present in plain 2.4. It might be a very
old bug in you rather old kernel, or one specific to some patches in
your distro's kernel (BTW, I would be surprized you wouldn't find
anything more recent than 2.4.17).
Best regards,
Willy
next prev parent reply other threads:[~2006-10-05 20:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-04 18:02 ip_conntrack_core - possible memory leak in 2.4 onovy
2006-10-04 18:09 ` Stephen Hemminger
2006-10-04 18:50 ` onovy
2006-10-05 19:30 ` Willy Tarreau [this message]
2006-10-05 21:55 ` onovy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20061005193028.GC5050@1wt.eu \
--to=w@1wt.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=netfilter-devel@lists.netfilter.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox