From: KOVACS Krisztian <hidden@balabit.hu>
To: security <security@lea-linux.com>
Cc: netfilter-devel <netfilter-devel@lists.netfilter.org>,
netfilter@lists.netfilter.org
Subject: Re: list delete bug: kernel crash
Date: Tue, 31 Aug 2004 12:50:37 +0200 [thread overview]
Message-ID: <1093949437.2435.4.camel@nienna.balabit> (raw)
In-Reply-To: <003701c48ee9$e1ad1f40$0a00a8c0@aziz>
Hi,
2004-08-31, k keltezéssel 01:34-kor security ezt írta:
> Aug 30 20:42:24 gateway kernel: NF_IP_ASSERT:
> net/ipv4/netfilter/ip_conntrack_core.c:1115(ip_conntrack_alter_reply)
> Aug 30 20:42:24 gateway kernel: NF_IP_ASSERT:
> net/ipv4/netfilter/ip_conntrack_core.c:1115(ip_conntrack_alter_reply)
> Aug 30 20:44:24 gateway kernel: LIST_DELETE:
> net/ipv4/netfilter/ip_conntrack_core.c:300
> `&ct->tuplehash[IP_CT_DIR_REPLY]'(f3cedca4) not in
> &ip_conntrack_hash[hr].
>
> I have search in bugzilla and google and, apparently, this bug has been solve
> since kernel 2.6.5.
> But i have kernel 2.6.8.1 and i have try kernel 2.6.6 and 2.6.7: same crash
>
> But it hard to "see" because i can stay 1 week without crash, or 5mn.
>
> I have the "local NAT" activated.
As always, the first thing you should try is testing the memory of
your computer. The problems seems to be caused by trying to call
ip_nat_setup_info() on an already confirmed connection, which is known
to cause hash corruption.
BTW, while running memtest, could you send us the nat table of your
iptables ruleset, along with the routing setup? And also a list of
loaded (iptables-related) kernel modules would be useful.
--
Regards,
Krisztian KOVACS
next prev parent reply other threads:[~2004-08-31 10:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-30 23:34 list delete bug: kernel crash security
2004-08-31 10:50 ` KOVACS Krisztian [this message]
2004-08-31 11:39 ` security
2004-08-31 13:17 ` security
2004-08-31 13:24 ` Gavin Hamill
2004-08-31 13:34 ` security
-- strict thread matches above, loose matches on Subject: below --
2004-08-31 14:18 security
2004-08-31 15:05 ` Gavin Hamill
2004-08-31 15:32 ` security
2004-08-31 16:01 ` Alistair Tonner
2004-08-31 22:19 ` security
2004-08-31 19:52 ` Jose Maria Lopez
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=1093949437.2435.4.camel@nienna.balabit \
--to=hidden@balabit.hu \
--cc=netfilter-devel@lists.netfilter.org \
--cc=netfilter@lists.netfilter.org \
--cc=security@lea-linux.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