From: "security" <security@lea-linux.com>
To: Gavin Hamill <gdh@acentral.co.uk>, netfilter@lists.netfilter.org
Subject: Re: list delete bug: kernel crash
Date: Tue, 31 Aug 2004 16:18:11 +0200 [thread overview]
Message-ID: <000801c48f65$58d3c940$0a00a8c0@aziz> (raw)
----- Original Message -----
From: "security" <security@lea-linux.com>
To: "Gavin Hamill" <gdh@acentral.co.uk>; <netfilter@lists.netfilter.org>
Sent: Tuesday, August 31, 2004 3:34 PM
Subject: Re: list delete bug: kernel crash
> >
>> This may be a long shot, but there may exist the possibility of the files
>> on
>> disk being corrupted when they were installed, due to your faulty memory?
>>
>> Try to reinstall the kernel / modules and iptables userspace?
>>
>> Cheers,
>> Gavin.
>>
>>
> Ok. I go re-compil my kernel and re-install iptable package :)
Ok still have crash after re-compil my kernel and re-install iptable
userspace package.
Allways the same error:
Aug 31 16:01:39 gateway kernel: LIST_DELETE:
net/ipv4/netfilter/ip_conntrack_core.c:300
`&ct->tuplehash[IP_CT_DIR_REPLY]'(d3ac9224) not in
&ip_conntrack_hash[hr].
Aug 31 16:01:39 gateway kernel: LIST_DELETE:
net/ipv4/netfilter/ip_conntrack_core.c:300
`&ct->tuplehash[IP_CT_DIR_REPLY]'(d3ac9524) not in
&ip_conntrack_hash[hr].
Aug 31 16:03:26 gateway kernel: LIST_DELETE:
net/ipv4/netfilter/ip_conntrack_core.c:300
`&ct->tuplehash[IP_CT_DIR_REPLY]'(d6537224) not in
&ip_conntrack_hash[hr].
next reply other threads:[~2004-08-31 14:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-31 14:18 security [this message]
2004-08-31 15:05 ` list delete bug: kernel crash 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
-- strict thread matches above, loose matches on Subject: below --
2004-08-30 23:34 security
2004-08-31 10:50 ` KOVACS Krisztian
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
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='000801c48f65$58d3c940$0a00a8c0@aziz' \
--to=security@lea-linux.com \
--cc=gdh@acentral.co.uk \
--cc=netfilter@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.