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 17:32:40 +0200 [thread overview]
Message-ID: <001101c48f6f$c080e0f0$0a00a8c0@aziz> (raw)
In-Reply-To: 200408311605.31805.gdh@acentral.co.uk
----- Original Message -----
From: "Gavin Hamill" <gdh@acentral.co.uk>
To: <netfilter@lists.netfilter.org>
Sent: Tuesday, August 31, 2004 5:05 PM
Subject: Re: list delete bug: kernel crash
> On Tuesday 31 August 2004 15:18, security wrote:
>
>> 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].
>
> That's a shame. Unless your netfilter support came via modules rather than
> from the kernel itself, then I'm afraid I have no more suggestions :( My
> last
> thinking was that you may not have replaced any modules - only the main
> kernel file...
>
I have re-compil / install kernel and modules.
But, i will wait because when the last crash occur, i had re install iptable
userspace BUT didn't have reboot.
And i have notice too that the iptable userspace i used was 1.2.11 compiled
by me, and now i have re-install offciel slackware 10.0 package: 1.2.10
So i will wait to see if i have other crash since i have reboot with this
iptable userspace version.
next prev parent reply other threads:[~2004-08-31 15:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-31 14:18 list delete bug: kernel crash security
2004-08-31 15:05 ` Gavin Hamill
2004-08-31 15:32 ` security [this message]
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='001101c48f6f$c080e0f0$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.