From: Rusty Russell <rusty@linuxcare.com.au>
To: safemode <safemode@voicenet.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: ip_conntrack locks up hard on 2.4.0 after about 10 hours
Date: Sun, 07 Jan 2001 22:27:29 +1100 [thread overview]
Message-ID: <E14FDyz-0004FK-00@halfway> (raw)
In-Reply-To: Your message of "Sat, 06 Jan 2001 10:37:54 CDT." <3A573BD2.C7F7771F@voicenet.com>
In message <3A573BD2.C7F7771F@voicenet.com> you write:
> It seems that for one reason or another, ip_conntrack totally locks (not
> removeable) after about 10 hours of continued use. All i found were
> these messages in my dmesg output
What was the contents of /proc/net/ip_conntrack?
Being unremovable can happen if someone is holding a packet, which the
below fix (by Xuan Baldauf) will often alleviate, but connection
tracking doesn't DROP packets (NAT and packet filtering do).
Hope that helps,
Rusty.
--
http://linux.conf.au The Linux conference Australia needed.
diff -urN -I \$.*\$ -X /tmp/kerndiff.RnRDbE --minimal linux-2.4.0-test13-3/net/ipv4/ip_input.c working-2.4.0-test13-3/net/ipv4/ip_input.c
--- linux-2.4.0-test13-3/net/ipv4/ip_input.c Tue Dec 12 14:28:06 2000
+++ working-2.4.0-test13-3/net/ipv4/ip_input.c Mon Dec 18 17:07:06 2000
@@ -225,6 +225,13 @@
nf_debug_ip_local_deliver(skb);
#endif /*CONFIG_NETFILTER_DEBUG*/
+#ifdef CONFIG_NETFILTER
+ /* Free reference early: we don't need it any more, and it may
+ hold ip_conntrack module loaded indefinitely. */
+ nf_conntrack_put(skb->nfct);
+ skb->nfct = NULL;
+#endif /*CONFIG_NETFILTER*/
+
/* Point into the IP datagram, just past the header. */
skb->h.raw = skb->nh.raw + iph->ihl*4;
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2001-01-07 23:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-06 15:37 ip_conntrack locks up hard on 2.4.0 after about 10 hours safemode
2001-01-06 15:51 ` safemode
2001-01-06 23:29 ` David S. Miller
2001-01-07 11:27 ` Rusty Russell [this message]
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=E14FDyz-0004FK-00@halfway \
--to=rusty@linuxcare.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=safemode@voicenet.com \
/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